linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Dave Chinner <david@fromorbit.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.35-r5 ext3 corruptions
Date: Fri, 23 Jul 2010 06:58:24 -0400	[thread overview]
Message-ID: <20100723105824.GA2205@infradead.org> (raw)
In-Reply-To: <20100723104313.GA6431@atrey.karlin.mff.cuni.cz>

On Fri, Jul 23, 2010 at 12:43:14PM +0200, Jan Kara wrote:
> changelog below. I'd much rather attribute the metadata corruption to a missing
> barrier option or barrier support in the virtualization stack. But I guess it's
> hard to tell now.

Any recent qemu/kvm stack has perfectly working barrier support.  Xen
is quite broken in that respect, but I hope no one is using that anyway.

But yes, with large write caches ext3 is rather broken due to the lack
of barriers.  Fortunately enough at least the enterprise enable it
anyway these days.

      parent reply	other threads:[~2010-07-23 10:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 10:57 2.6.35-r5 ext3 corruptions Dave Chinner
2010-07-15 11:26 ` Dave Chinner
2010-07-15 18:23 ` Josef Bacik
2010-07-15 20:14 ` Johannes Hirte
2010-07-19 22:45 ` Dave Chinner
2010-07-21  6:32   ` Dave Chinner
2010-07-21 11:07     ` Török Edwin
2010-07-21 14:01       ` Eric Sandeen
2010-07-21 13:55     ` Eric Sandeen
2010-07-23 10:43     ` Jan Kara
2010-07-23 10:53       ` Jan Kara
2010-07-23 10:55         ` Dave Chinner
2010-07-23 10:58       ` Christoph Hellwig [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=20100723105824.GA2205@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).