search for: jbd_preclean_buffer_check

...Trace; c0003f5c <ret_from_syscall_1+0/b4> Trace; 00000000 Before first symbol Trace; 10002018 Before first symbol Trace; 100019a8 Before first symbol Trace; 10001b54 Before first symbol Trace; 6fed6478 Before first symbol Trace; 00000000 Before first symbol Followed by: Assertion failure in jbd_preclean_buffer_check() at jbd-kernel.c:74: "(jh->b_jlist == 0 || jh->b_jlist == 7 || jh->b_jlist == 5 || jh->b_jlist == 4 || buffer_jbd_data(bh))" kernel BUG at jbd-kernel.c:74! Oops: Exception in kernel mode, sig: 4 NIP: C00538E0 XER: 00000000 LR: C00538E0 SP: C594BDE0 REGS: c594bd30 TRAP: 0700 U...

...now. Whenever I see this happen, I always reboot the system, since I am not sure how serious the problem is. The assert text is as follows: -- cut here -- cut here -- cut here -- cut here -- cut here -- Message from syslogd@dax at Tue Oct 9 12:07:47 2001 ... dax kernel: Assertion failure in jbd_preclean_buffer_check() at jbd-kernel.c:80: "(((bh)->b_state & (1UL << BH_Dirty)) != 0)" -- cut here -- cut here -- cut here -- cut here -- cut here -- Here is line 80 from jbd-kernel.c: -- cut here -- cut here -- cut here -- cut here -- cut here -- J_ASSERT_JH(jh, buf...

...e for some reason. I've tested this pretty hard, every which way. It looks OK. There was a report against ext3-for-2.4.10 that mark_buffer_clean() was being called against an already-clean buffer. This has not been reproducable (in later kernels, at least). If anyone sees the message "jbd_preclean_buffer_check: clean of clean buffer" come out, please shout. This can only happen if ext3 debugging support is enabled in config.