[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: 2.2.19: Assertion failure in ext3_new_block() at balloc.c line 709



Hi,

On Thu, Dec 06, 2001 at 10:43:59AM +0100, Giulio Orsero wrote:
> On Thu, 06 Dec 2001 10:31:10 +0100, you wrote:
> 
> >0149b27>] [<c0149ccc>]
> >       [<c014bb4b>] [<c012ee8f>] [<c012f57d>] [<c010a06c>] [<c010002b>]
> >Code: c6 05 00 00 00 00 00 83 c4 14 90 b8 0d 00 00 00 0f b3 45 18
> > 
> >>>EIP; c0146885 <ext3_new_block+635/738>   <=====
> >Trace; c01f2fff <cprt+2a1f/a240>
> 
> After reboot, raid1 resync was running, I retried untarring the same file in
> the same conditions (from raid1/ext3 to ext3 non raid):
> 
> Assertion failure in jfs_prelock_buffer_check() at journal.c line 411:
> "bh->b_jlist == 0 || bh->b_jlist == BJ_LogCtl || bh->b_jlist == BJ_IO ||
> bh->b_jlist == BJ_Data"

That is expected: ext3 is completely incompatible with raid1 and raid5
on 2.2 kernels (it's a raid problem).  You need to run 2.4 if you want
it to work.  The major problem is during resync, but because it's a
showstopper, we haven't tested ext3 over raid during normal running
on 2.2 at all.

The only workaround is to wait until raid resync has finished before
doing any writes to the filesystem.

Cheers,
 Stephen





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]