(Not CCing everyone, since this is mostly curiosa in the "using git as it was never intended" section): On Monday 19 October 2009 13:03:42 Junio C Hamano wrote: > Once a packfile is created and we always use it read-only, there didn't > seem to be much point in suspecting that the underlying filesystems or > disks may corrupt them in such a way that is not caught by the SHA-1 > checksum over the entire packfile and per object checksum. That trust in > the filesystems might have been a good tradeoff between fsck performance > and reliability on platforms git was initially developed on and for, but > it might not be true anymore as we run on more platforms these days. Filesystems are mostly reliable, but only until your crazy users do strange and terrible things. I have a real, non-toy environment where I use this stack as a [horrible] workaround for some issues beyond my control: git -> ext4 -> lvm -> dmcrypt -> loop -> sshfs -> cygwin sshd -> SMB share Amazingly, this works pretty reliably with many gigabytes of data in a git repository, even with the occasional crash because of flakiness with the "sshfs -> cygwin sshd" piece of the puzzle. But a good "git fsck" sure doesn't hurt in this environment! =) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html