From: David Brown <git@davidb.org>
To: Luciano Rocha <luciano@lsd.di.uminho.pt>
Cc: Luke Diamand <luke@diamand.org>, git@vger.kernel.org
Subject: Re: git repo being corrupted?
Date: Mon, 7 Apr 2008 09:15:25 -0700 [thread overview]
Message-ID: <20080407161525.GA25894@old.davidb.org> (raw)
In-Reply-To: <20080407113921.GA13667@bit.office.eurotux.com>
On Mon, Apr 07, 2008 at 12:39:21PM +0100, Luciano Rocha wrote:
>> > You're using XFS. Did you have a power fail in the recent past?
>>
>> How did you know?
>
>XFS doesn't order metadata writes with data writes, so if the power
>fails, it can find an update in the journal but the data wasn't written.
>Then it fills the file with zeroes to the new size.
This behavior should be a lot better for recent kernels.
xfs does even better with write barriers. But any file change that is more
than one write can be corrupted or split by an inopportune powerdown.
David
next prev parent reply other threads:[~2008-04-07 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 10:04 git repo being corrupted? Luke Diamand
2008-04-07 11:17 ` Luciano Rocha
2008-04-07 11:21 ` Luke Diamand
2008-04-07 11:39 ` Luciano Rocha
2008-04-07 16:15 ` David Brown [this message]
2008-04-07 16:47 ` Luciano Rocha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080407161525.GA25894@old.davidb.org \
--to=git@davidb.org \
--cc=git@vger.kernel.org \
--cc=luciano@lsd.di.uminho.pt \
--cc=luke@diamand.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).