Hello.
There is a git-annex repository managing about 172.000 annexed files (plus a number of small regular files in git history), for a total of about 1.7TB. At filesystem level, find reports about 924.000 entries (directories, files, symlinks).
Inspecting it I see that .git/annex/transfer containes over 86000 entries (mostly files).
I tried to find more information about it and only https://git-annex.branchable.com/design/assistant/syncing/ seemed to provide some information but not enough.
Are they needed permanently? Can I just delete .git/annex/transfer without damage?
Thanks.
I'm not certain, but I think
will work.
This (quickly) finds only two entries: one regarding a file in
.git/annex/transferand one other in.git/annex/bad/.Anyway,
git annex drop --unusedis too general and would potentially involve a number of other files.I'm just considering something that should probably be safe:
unless people tell me it's dangerous somehow. Having to do a
git annex fsckin the future is okay. Having important features broken until I do agit annex fsck(or worse) is less cool.It's fine to delete .git/annex/transfer/ at any time.
Those files are used to make
git annex info(and the webapp) be able to show what transfers are in progress. Normally they're cleaned up when a transfer finishes; if you interrupt git-annex they will be left behind.Running
git annex infois also supposed to clean up the stale transfer info files, but it was broken -- now fixed.The only time you get files in .git/annex/bad/ is when fsck finds a file got corrupted somehow and moves its content there. It's fine to delete those unless you were planning to recover or examine the corrupted file in some way.