From: Andrew Morton <akpm@linux-foundation.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
bugme-daemon@bugzilla.kernel.org, h.judt@gmx.at
Subject: Re: [Bug 9692] New: journal_data mount option causes filesystem corruption with blocksize != 4096
Date: Tue, 26 Feb 2008 13:48:52 -0800 [thread overview]
Message-ID: <20080226134852.04ddada7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080105191552.ee114b6b.akpm@linux-foundation.org>
On Sat, 5 Jan 2008 19:15:52 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Sat, 5 Jan 2008 09:52:15 -0800 (PST) bugme-daemon@bugzilla.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@osdl.org
> > ReportedBy: h.judt@gmx.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.
prev parent reply other threads:[~2008-02-26 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9692-27@http.bugzilla.kernel.org/>
2008-01-06 3:15 ` [Bug 9692] New: journal_data mount option causes filesystem corruption with blocksize != 4096 Andrew Morton
2008-02-26 21:48 ` Andrew Morton [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=20080226134852.04ddada7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=h.judt@gmx.at \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.