Is there a way to make fsck only display corrupted files instead of move them to the internal /bad folder?
Especially since the -q option (to only print corrupted files) doesn't even print the filename, only that a file has been moved...it seems a bit aggressive to compulsorily move a file to some obfuscated name AND not indicate its original location anywhere...
I've made fsck -q include the name of the file in that warning message.
Note that, given any file in
.git/annex/bad, you can find the files in the git repository that linked to it, by runninggit log --stat -S$filenameDo you mean "made"=="updated" or made=="already exists"?
Maybe I have an old version (installed via brew)...
I get:
~/s/a/annex8 git:master ❯❯❯ git annex fsck -q Bad file size (1 B smaller); moved to .git/annex/bad/ git-annex: fsck: 1 failed
unless there are no other copies, in which case the original filename it is printed on a new line with the "No known copies" warning.
My use-case is for images - a small amount of corruption to some old images might not be visually perceptible, and hence tolerable, especially if I'm short-sighted enough to only have 1 copy. I mean its possible for the user to navigate to /bad, visually inspect that they're ok with a corrupted image, parse the git log --stat message and restore it. But it seems beneficial to have something like a rsync-like "--dryrun" option for fsck.