On Sat, 5 Jan 2008 19:15:52 -0800 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > On Sat, 5 Jan 2008 09:52:15 -0800 (PST) bugme-daemon@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxx > > ReportedBy: h.judt@xxxxxx > > > > > > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
