On Mon, Jul 15, 2013 at 01:48:23PM -0400, Greg Troxel wrote:
I am curious if anyone has actual experiences to share, either
a report of corruption after a crash (where corruption means that
either 1) git fsck reports worse than dangling objects or 2) some ref
did not either point to
Am 7/15/2013 19:48, schrieb Greg Troxel:
Clearly there is the possibility of creating a corrupt repository when
receiving objects and updating refs, if a crash or power failure causes
data not to get written to disk but that data is pointed to. Journaling
mitigates this, but I'd argue that
Clearly there is the possibility of creating a corrupt repository when
receiving objects and updating refs, if a crash or power failure causes
data not to get written to disk but that data is pointed to. Journaling
mitigates this, but I'd argue that programs should function safely with
only the
Greg Troxel wrote:
Alternatively, is there somewhere a first-principles analysis vs POSIX
specs (such as fsyncing object files before updating refs to point to
them, which I realize has performance negatives)?
You might be interested in the 'core.fsyncobjectfiles' setting.
git-config(1) has
4 matches
Mail list logo
