Am 21.06.2015 um 15:59 schrieb Christoph Hellwig: > On Sun, Jun 21, 2015 at 03:07:41PM +0200, Richard Weinberger wrote: >>>> To me it seems like git was creating a new object and got interrupted >>>> before fsync/fdatasync'ing it. >>>> As the object was referenced before syncing the data to disk the repo broke. > > Git doesn't fsync by default, and because of that I've seen similar > data losses on ext4/xfs/btrfs. > > You can set the core.fsyncobjectfiles to mitigate it, but even with > that I've seen corrupted index files. Yeah, after inspecting git's source I've found that config option too. Now it's also crystal clear that git is not power cut safe at all by default. ;-\ So, anyone that cares about his repos has to enable core.fsyncobjectfiles, which is IMHO kind of sad. Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
