This commit is contained in:
parent
92877bb5d0
commit
e191f127eb
1 changed files with 22 additions and 0 deletions
|
@ -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: <http://git-annex.branchable.com/tips/unlocked_files>
|
||||
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
|
Loading…
Reference in a new issue