[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20080226134852.04ddada7.akpm@linux-foundation.org>
Date: Tue, 26 Feb 2008 13:48:52 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Theodore Ts'o" <tytso@....edu>
Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
bugme-daemon@...zilla.kernel.org, h.judt@....at
Subject: Re: [Bug 9692] New: journal_data mount option causes filesystem
corruption with blocksize != 4096
On Sat, 5 Jan 2008 19:15:52 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Sat, 5 Jan 2008 09:52:15 -0800 (PST) bugme-daemon@...zilla.kernel.org wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=9692
> >
> > Summary: journal_data mount option causes filesystem corruption
> > with blocksize != 4096
> > Product: File System
> > Version: 2.5
> > KernelVersion: 2.6.23.9
> > Platform: All
> > OS/Version: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: high
> > Priority: P1
> > Component: ext3
> > AssignedTo: akpm@...l.org
> > ReportedBy: h.judt@....at
> >
> >
> > Most recent kernel where this bug did not occur: -
> > Older kernels have this problem too (I think I noticed this booting >= 2.6.21,
> > definitely 2.6.22).
>
> I'm getting the feeling that we should just disable data=journal. Make it
> use data=ordered mode instead. It isn't getting a lot of attention..
>
As discussed today - this is the bug which makes me wonder how
useful/popular journalled-data mode is.
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists