From e191f127eb0727ce08a1399813ee700788f2af53 Mon Sep 17 00:00:00 2001 From: "susetux@ed6f4e20192c3eae018e1fc6442bf993d41b3848" Date: Sun, 13 Mar 2016 11:16:09 +0000 Subject: [PATCH] --- ...v5_repo_to_an_always_unlocked_v6_repo.mdwn | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn 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 new file mode 100644 index 0000000000..4eec48138a --- /dev/null +++ b/doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn @@ -0,0 +1,22 @@ +Hi, +I'm trying to convert a v5 classic, symlink repository into a v6 always unloked repository. + + +I'm trying to follow along with: +but something goes wrong in the process, so I'm sure I'm missing something. +The repository is about 600G to start with and I don't have another 600G of free space on disk, so I'm going with thin mode: + +1. git annex upgrade +2. git config annex.thin true +3. git annex fix +4. git annex unlock + +It's all good to this point. Everything gets unlocked and is fine. +Then I try to commit the changes with "git annex sync" and the process seems to take +and incredibly long time (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? + +thanks a lot, daniel