summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar susetux@ed6f4e20192c3eae018e1fc6442bf993d41b3848 <susetux@web>2016-03-13 11:32:35 +0000
committerGravatar admin <admin@branchable.com>2016-03-13 11:32:35 +0000
commitd80fc9db8c98f02181a5a3de56e8e8e6b17e2dda (patch)
treeb903bc4ccb506d04c447ef7d522c616e39d99ffc
parent4006856689b70dd26967e37b77c8b9d28fc4f969 (diff)
-rw-r--r--doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn b/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn
index 77731fefe..40735383a 100644
--- a/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn
+++ b/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn
@@ -20,6 +20,15 @@ The process seems to take
and incredibly long time (several hours) and then ends up running out of space. I check the repository with "du -sh"
and it's almost double the size. Is there a reason for this? Is there a way to avoid this duplication of data. Shouldn't annex.thin do the trick?
+This is also strange: with "git annex info" I get
+
+ local annex keys: 3572
+ local annex size: 933.19 gigabytes
+ annexed files in working tree: 0
+ size of annexed files in working tree: 0 bytes
+
+the annex size should be about 540G and why are there no annexed files in the working tree?
+
Is there a correct and faster way to migrate my repo to an always unlocked one which won't require hours of time and take all that disk space?
thanks a lot, daniel