From: Luciano Rocha <luciano@lsd.di.uminho.pt>
To: Luke Diamand <luke@diamand.org>, git@vger.kernel.org
Subject: Re: git repo being corrupted?
Date: Mon, 7 Apr 2008 17:47:38 +0100 [thread overview]
Message-ID: <20080407164738.GA4053@bit.office.eurotux.com> (raw)
In-Reply-To: <20080407161525.GA25894@old.davidb.org>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Mon, Apr 07, 2008 at 09:15:25AM -0700, David Brown wrote:
> 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.
To be fair, it hasn't happened to me lately. But I haven't lost power
often, so I can't say it's fixed. ;)
> 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.
Maybe, but I'm still waiting for barrier support through device-mapper.
--
lfr
0/0
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-04-07 16:48 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
2008-04-07 16:47 ` Luciano Rocha [this message]
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=20080407164738.GA4053@bit.office.eurotux.com \
--to=luciano@lsd.di.uminho.pt \
--cc=git@vger.kernel.org \
--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).