mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Browse source
This commit is contained in:
susetux@ed6f4e20192c3eae018e1fc6442bf993d41b3848 2016-03-13 11:19:39 +00:00 committed by admin
parent e191f127eb
commit a1765ecf8c
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/forum/converting_a_v5_repo_to_an_always_unlocked_v6_repo.mdwn
View file

@ -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 4. git annex unlock
It's all good to this point. Everything gets unlocked and is fine. 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 Then I try to commit the changes with:
and incredibly long time (hours) and then ends up running out of space. I check the repository with "du -sh"
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? 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) Should I not have done the sync thing? (I need to sync with other repos too after the migration is done)