From b28f32e47f4c6b3b2003194fe62c95ae013ac5d7 Mon Sep 17 00:00:00 2001 From: "susetux@ed6f4e20192c3eae018e1fc6442bf993d41b3848" Date: Sun, 13 Mar 2016 11:20:49 +0000 Subject: [PATCH] --- .../converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn | 3 +-- 1 file changed, 1 insertion(+), 2 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 7c42094fa0..11ff6116b0 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 @@ -19,8 +19,7 @@ Then I try to commit the changes with: 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? -Should I not have done the sync thing? (I need to sync with other repos too after the migration is done) -Is there a correct way to migrate my repo to an always unlocked one which won't require hours of time and take all that disk space? +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