Re: BUG: Assertion failure with ext3-0.95 for 2.4.7

[Christian Borntraeger]

>Well ext3 has more debugging checks than ext3 at the moment, and also
requires the
>underlying blocklayers (LVM/RAID etc) to not lie. So the test _IS_
relevant,
>not to caste blame, but to find the interaction.....

OK, I tried it now  with md  and the bug was there again. Now during a rm
-rf * .
As the bug ouccured with LVM __and__  with MD it looks like a ext3-problem.
Tom Rini reported the same problem on a PPC-Box. Possibly it is a big
endian problem.

The message was again:
kernel: Assertion failure in journal_forget() at transaction.c:1184:
"!jh->b_committed_data"

Here a have a new backtrace, I resolved the functions manually from
system.map -hopefully without a mistake.

kernel BUG at transaction.c:1184!
illegal operation: 0001
CPU:    1
Process rm (pid: 1917, stackpage=06125000)

Kernel PSW:    070c0000 8008023c   =journal_forget
task: 06124000 ksp: 06125938 pt_regs: 061258a0
Kernel GPRS:
00000000  8001c118  00000022  00000001
8008023a  00c2a000  00197198  00000001
12fc1880  08d06494  00001899  1575c9b0
0001f94c  800800ac  8008023a  06125938
Kernel ACRS:
00000000  00000000  00000000  00000000
00000001  00000000  00000000  00000000
00000000  00000000  00000000  00000000
00000000  00000000  00000000  00000000
Kernel BackChain  CallChain
       06125938   [<0008023a>]           =journal_forget
       061259a0   [<000747e6>]           =ext3_forget
       06125a08   [<00076c00>]           =ext3_clear_blocks
       06125a70   [<00076d20>]           =ext3_free_data
       06125ae8   [<00076ee4>]           =ext3_free_branches
       06125b60   [<00076e44>]           =ext3_free_branches
       06125bd8   [<00076e44>]           =ext3_free_branches
       06125c50   [<0007723c>]           =ext3_truncate

greetings