diff options
author | Joey Hess <joey@kitenet.net> | 2011-03-09 15:59:44 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2011-03-09 15:59:44 -0400 |
commit | 9229d182d32570f6829ced655aa673ceddfe7693 (patch) | |
tree | d8a49ed7ae7733495bc93ddf8262fe8a16cc056b /doc/walkthrough | |
parent | b5134b4716c266147a35353316686cf29658350d (diff) |
update
Diffstat (limited to 'doc/walkthrough')
-rw-r--r-- | doc/walkthrough/recover_data_from_lost+found.mdwn | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/walkthrough/recover_data_from_lost+found.mdwn b/doc/walkthrough/recover_data_from_lost+found.mdwn new file mode 100644 index 000000000..6e2c24148 --- /dev/null +++ b/doc/walkthrough/recover_data_from_lost+found.mdwn @@ -0,0 +1,17 @@ +Suppose something goes wrong, and fsck puts all the files in lost+found. +It's actually very easy to recover from this disaster. + +First, check out the git repository again. Then, in the new checkout: + + mkdir recovered-content + sudo mv ../lost+found/* recovered-content + git annex add recovered-content + git rm recovered-content + git commit -m "recovered some content" + git annex fsck + +The way that works is that when git-annex adds the same content that was in +the repository before, all the old links to that content start working +again. This works particularly well if the SHA1 backend is used, but even +with the default backend it will work pretty well, as long as fsck +preserved the modification time of the files. |