Ext4 + barriers=1 + ssd + power loss while commiting to a git repo = broken repo?

[Andreas Schwab]

Michał Piotrowski <mkkp4x4 at gmail.com> writes:

> W dniu 14 kwietnia 2011 11:04 użytkownik Andreas Schwab
> <schwab at redhat.com> napisał:
>> Michał Piotrowski <mkkp4x4 at gmail.com> writes:
>>
>>> But the question remains - should enabled barriers protect against
>>> such data loss/breakage? Or I just had a big bad luck?
>>
>> It could also be a bug in git, perhaps it needs to take more care to
>> create the ref file atomically.
>
> Should I report it to upstream or in bugzilla.redhat.com?

Looking closer it seems like git already does the right thing
(open("master.lock"), write(sha1), rename("master.lock", "master")), so
it appears to be a barriers issue.

> It seems to me that the repairing git repo without a deep knowledge of
> it can be rather difficult.

gitrepository-layout(5)

Andreas.

-- 
Andreas Schwab, schwab at redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84  5EC7 45C6 250E 6F00 984E
"And now for something completely different."