diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-02-27 12:45:48 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-02-27 12:45:48 -0400 |
| commit | 98e246b49b3c4fed319fe7bc1e900ba20ebfc9e1 (patch) | |
| tree | ad49ec6baf1b57f3acc8b694bdfc1bbd0986021f /doc/walkthrough/fsck:_when_things_go_wrong.mdwn | |
| parent | 9e49a71282def0b6d6f7507d59eb0f805c6e0073 (diff) | |
split the walkthrough and inline back together
Diffstat (limited to 'doc/walkthrough/fsck:_when_things_go_wrong.mdwn')
| -rw-r--r-- | doc/walkthrough/fsck:_when_things_go_wrong.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/walkthrough/fsck:_when_things_go_wrong.mdwn b/doc/walkthrough/fsck:_when_things_go_wrong.mdwn new file mode 100644 index 000000000..05b9f385c --- /dev/null +++ b/doc/walkthrough/fsck:_when_things_go_wrong.mdwn @@ -0,0 +1,13 @@ +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: + + # git annex fsck + fsck my_cool_big_file (checksum...) + git-annex: Bad file content; moved to .git/annex/bad/SHA1:7da006579dd64330eb2456001fd01948430572f2 + git-annex: ** No known copies of the file exist! + 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 |