Hi,
I noticed recently a worrying git behavior. I often do something like that: git fsck --full git gc git push origin master | backup of the entire tree in tar archive
'git fsck' or 'git gc' sometimes causes damage to the repository ie:
$ git fsck --full error: packed 694728b9fe62ad667f051a109c389403ffa0cb29 from .git/objects/pack/pack-a4bae2576b36116f1962a5496674ea921eebb6c5.pack is corrupt
This time, however, after 'git fsck' rerun I don't get this error message, but in other cases, the repository is corrupted. Has anyone noticed similar problems with git on F16?
Michał Piotrowski mkkp4x4@gmail.com writes:
Hi,
I noticed recently a worrying git behavior. I often do something like that: git fsck --full git gc git push origin master | backup of the entire tree in tar archive
'git fsck' or 'git gc' sometimes causes damage to the repository ie:
$ git fsck --full error: packed 694728b9fe62ad667f051a109c389403ffa0cb29 from .git/objects/pack/pack-a4bae2576b36116f1962a5496674ea921eebb6c5.pack is corrupt
This time, however, after 'git fsck' rerun I don't get this error message, but in other cases, the repository is corrupted. Has anyone noticed similar problems with git on F16?
Linus wrote nice document about recovering corrupted blob
http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/howto/recover-co...
2012/3/14 Nikola Pajkovsky npajkovs@redhat.com:
Michał Piotrowski mkkp4x4@gmail.com writes:
Hi,
I noticed recently a worrying git behavior. I often do something like that: git fsck --full git gc git push origin master | backup of the entire tree in tar archive
'git fsck' or 'git gc' sometimes causes damage to the repository ie:
$ git fsck --full error: packed 694728b9fe62ad667f051a109c389403ffa0cb29 from .git/objects/pack/pack-a4bae2576b36116f1962a5496674ea921eebb6c5.pack is corrupt
This time, however, after 'git fsck' rerun I don't get this error message, but in other cases, the repository is corrupted. Has anyone noticed similar problems with git on F16?
Linus wrote nice document about recovering corrupted blob
http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/howto/recover-co...
Thanks for sharing this link. This is a lot of git magic and I prefer to do backups :)
"The most common cause of corruption so far has been memory corruption" - it gives me food for thought.
I am using the SSD with Ext4 - I checked it recently with "fsck.ext4 -cvf", it may also be useful to check RAM.
-- Nikola -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel