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

Added a comment

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus 2011-04-03 16:02:33 +00:00 committed by admin
parent 5f3385ce3b
commit 862df8aa21
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_16_8a4ab1af59098f4950726cf53636c2b3._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
nickname="Jimmy"
subject="comment 16"
date="2011-04-03T16:02:33Z"
content="""
I think the correct steps should be, make a backup first :) then ...
1. git pull # update your clone, and commit everything so you don't lose anything
2. git annex fsck --fast # check the repo first, just in case
3. rm -rf .git-annex/?? # remove the old metadata
4. git annex fsck --fast # get git annex to regenerate it all
5. push your changes out to your other repos, you will need to make sure git-annex is updated everywhere if there are remotes in your setup.
I eventually migrated all of my own annex'd repos and I no longer have the old hashed directories but the new ones in the form
.git/annex/aaa/bbb/foo.log
I did lose some tracking information but not data (as far as I can see for now), but that was quickly fixed by pushing and pulling to my bare repo which tracks most of my data.
I also found that it worked a bit more reliably for me on the copies of repos that were located on case sensitive filesystems, but I guess that was expected.
"""]]