summaryrefslogtreecommitdiff
path: root/doc/walkthrough/recover_data_from_lost+found.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/walkthrough/recover_data_from_lost+found.mdwn')
-rw-r--r--doc/walkthrough/recover_data_from_lost+found.mdwn14
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/walkthrough/recover_data_from_lost+found.mdwn b/doc/walkthrough/recover_data_from_lost+found.mdwn
index 6e2c24148..f101b3caf 100644
--- a/doc/walkthrough/recover_data_from_lost+found.mdwn
+++ b/doc/walkthrough/recover_data_from_lost+found.mdwn
@@ -3,12 +3,14 @@ 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
+ $ 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