[lkml]   [2001]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Define conflict between ext3 and raid patches against 2.2.19
On Wednesday September 19, wrote:
> On Tue, Sep 18, 2001 at 09:08:32PM +1000, Neil Brown wrote:
> >
> > You should be aware that ext3 (and other journalling filesystems) do
> > not work reliably over RAID1 or RAID5 in 2.2. Inparticular, you can
> > get problems when the array is rebuilding/resyncing.
> >
> > But if you only plan to use ext3 with raid0 or linear, you should be
> > fine.
> >
> Can you point me to an archive that describes how to trigger this bug?
> Was it in linux-raid or ext3-users or ...?
> Mike

I don't remember exactly where or when I read it - either linux-raid
or linux-kernel. It was asserted by Stephen Tweedie.

The problem is that ext3 is very careful about when it writes buffer
to disk : it won't release a buffer until the relevant journal entry
is committed.

However when a RAID rebuild happens, every block on the array is read
into the buffer cache (if it isn't already there) and then written
back out again. This defeats the control that ext3 tries to maintain
on the buffer cache.

I don't know exactly what large-scale effects this might have. It
could be simply that a crash at the wrong time could leave the
filesystem corrupted. But I heard of one person who claimed to get
filesystem corruption after using reiserfs over RAID1 in 2.2, so maybe
it's worse than that.

If you really need to know, I suggest you ask on ext3-users.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.069 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site