From 0d9f3bdae07ac067af942606b2b56a9ef06390ae Mon Sep 17 00:00:00 2001 From: "susetux@ed6f4e20192c3eae018e1fc6442bf993d41b3848" Date: Sun, 13 Mar 2016 11:32:35 +0000 Subject: [PATCH] --- ...nverting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) 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 77731fefe2..40735383ae 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