diff options
| author |  susetux@ed6f4e20192c3eae018e1fc6442bf993d41b3848 <susetux@web> | 2016-03-13 11:19:39 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-03-13 11:19:39 +0000 |
| commit | 1387bfc732edc1c6c69c1d985ca42b1bff51797c (patch) | |
| tree | 2c270fe0d1af2d5742f3184f9cc08e9dd5783c41 | |
| parent | 18a3e74c34f97c1e4c7d30e6458044d767309f35 (diff) | |
| -rw-r--r-- | doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn | 8 |
1 files changed, 6 insertions, 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 4eec48138..7c42094fa 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 @@ -12,8 +12,12 @@ The repository is about 600G to start with and I don't have another 600G of free 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" +Then I try to commit the changes with: + + git annex sync + +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) |