diff options
author | 2011-10-17 13:56:36 -0400 | |
---|---|---|
committer | 2011-10-17 13:56:36 -0400 | |
commit | 617bdc740f76e0b5cb8d73a8b122cd2b3e6fe961 (patch) | |
tree | 92c932685e19b1df6bd453810e9a4052cdf92f3e /doc/walkthrough/recover_data_from_lost+found.mdwn | |
parent | 66fa4c947c30ca9848121912229f3e84a855a74f (diff) |
reorg
Diffstat (limited to 'doc/walkthrough/recover_data_from_lost+found.mdwn')
-rw-r--r-- | doc/walkthrough/recover_data_from_lost+found.mdwn | 19 |
1 files changed, 0 insertions, 19 deletions
diff --git a/doc/walkthrough/recover_data_from_lost+found.mdwn b/doc/walkthrough/recover_data_from_lost+found.mdwn deleted file mode 100644 index 48ef2a1d7..000000000 --- a/doc/walkthrough/recover_data_from_lost+found.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -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 - $ sudo chown you:you recovered-content - $ chmod -R u+w 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 SHA* backends are used, but even -with the default backend it will work pretty well, as long as fsck -preserved the modification time of the files. |