2011-02-27 16:45:48 +00:00
|
|
|
Fsck never deletes possibly bad data; instead it will be moved to
|
|
|
|
|
`.git/annex/bad/` for you to recover. Here is a sample of what fsck
|
|
|
|
|
might say about a badly messed up annex:
|
|
|
|
|
|
2019-03-27 15:15:03 +00:00
|
|
|
$ git annex fsck
|
2011-02-27 16:45:48 +00:00
|
|
|
fsck my_cool_big_file (checksum...)
|
|
|
|
|
git-annex: Bad file content; moved to .git/annex/bad/SHA1:7da006579dd64330eb2456001fd01948430572f2
|
2011-06-23 23:56:24 +00:00
|
|
|
git-annex: ** No known copies exist of my_cool_big_file
|
2011-02-27 16:45:48 +00:00
|
|
|
failed
|
|
|
|
|
fsck important_file
|
|
|
|
|
git-annex: Only 1 of 2 copies exist. Run git annex get somewhere else to back it up.
|
|
|
|
|
failed
|
|
|
|
|
git-annex: 2 failed
|
