Hi all,
Sorry for the repost. If I should be asking somewhere else please tell me where.
I woke up a few days ago to find this on one of my machines.
Below is hopefully the revelent output from dmesg and /var/log/messages. I
have had this b4 but this is the first time I have been able to get any useful
information from it. The machine usually locks and all I see is the assertion
failure on the console. This is a stock 7.2 system with all revelant updates.
FWIW this appears to have happened about the time the cron.daily stuff
ran (logrotate updatedb etc). The machine has been up for approx 36 days.
Not sure what other info to provide so if I missed something please let me
know.
Can someone please tell me what this means?? Is there enough info to tell what
happened here?
############################### Begin dmesg
#######################################
Output from dmesg:
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
hdc: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hdc: status timeout: status=0xd0 { Busy }
hdd: DMA disabled
hdc: drive not ready for command
ide1: reset: success
EXT3-fs error (device ide1(22,65)): ext3_readdir: bad entry in directory
#2665467: rec_len % 4 != 0 - offset=0, inode=762621470, rec_len=44574,
name_len=110
Assertion failure in journal_bmap_Rbbdc8009() at journal.c:602: "ret !=
0"
------------[ cut here ]------------
kernel BUG at journal.c:602!
invalid operand: 0000
Kernel 2.4.9-31
CPU: 0
EIP: 0010:[<c8805368>] Not tainted
EFLAGS: 00010286
EIP is at journal_bmap_Rbbdc8009 [jbd] 0x58
eax: 0000001d ebx: 00000000 ecx: c02af5c4 edx: 00001f06
esi: c3a7f640 edi: 00000000 ebp: c45c5800 esp: c71ffe50
ds: 0018 es: 0018 ss: 0018
Process kjournald (pid: 148, stackpage=c71ff000)
Stack: c88093af 0000025a c45c5800 c88052ff c45c5800 000014ed c45c5800 c880538b
c45c5800 c3a7f640 c8802811 c45c5800 c45c58e4 00000000 00000000 00000000
00000000 c5583aa0 c20a2960 c0b87640 000000f0 c1498ae0 c033ab9c c019f880
Call Trace: [<c88093af>] __insmod_jbd_S.rodata_L96 [jbd] 0x285f
[<c88052ff>] log_wait_commit_R6c342301 [jbd] 0xcf
[<c880538b>] journal_bmap_Rbbdc8009 [jbd] 0x7b
[<c8802811>] journal_flushpage_R40b21025 [jbd] 0xa21
[<c019f880>] do_rw_disk [kernel] 0x150
[<c011317e>] schedule [kernel] 0x26e
[<c8804e3b>] journal_revoke_R67623458 [jbd] 0x5eb
[<c8804d10>] journal_revoke_R67623458 [jbd] 0x4c0
[<c0105726>] kernel_thread [kernel] 0x26
[<c8804d30>] journal_revoke_R67623458 [jbd] 0x4e0
Code: 0f 0b 59 58 eb 04 89 f6 89 c3 89 d8 5b c3 8d 76 00 8d bc 27
############################ END OF DMESG ################################
Output from /var/log/messages:
Apr 25 04:35:53 kanga syslogd 1.4.1: restart.
Apr 25 04:36:48 kanga rpc.mountd: authenticated unmount request from
192.168.0.250:775 for /home/mirrors/ftp (/home/mirrors/ftp)
Apr 25 04:36:49 kanga automount[17559]: expired /kanga/ftp
Apr 25 04:37:12 kanga kernel: EXT3-fs error (device ide1(22,65)): ext3_readdir:
bad entry in directory #2665467: rec_len %% 4 != 0 - offset=0, inode=762621470,
rec_len=44574, name_len=110
Apr 25 04:37:13 kanga kernel: Assertion failure in journal_bmap_Rbbdc8009() at
journal.c:602: "ret != 0"Apr 25 04:37:13 kanga kernel: ------------[
cut here ]------------
Apr 25 04:37:13 kanga kernel: kernel BUG at journal.c:602!
Apr 25 04:37:13 kanga kernel: invalid operand: 0000
Apr 25 04:37:13 kanga kernel: Kernel 2.4.9-31
Apr 25 04:37:13 kanga kernel: CPU: 0
Apr 25 04:37:14 kanga kernel: EIP:
0010:[wd:__insmod_wd_O/lib/modules/2.4.9-31/kernel/drivers/net/wd.o_+-244888/96]
Not tainted
Apr 25 04:37:14 kanga kernel: EIP: 0010:[<c8805368>] Not tainted
Apr 25 04:37:14 kanga kernel: EFLAGS: 00010286
Apr 25 04:37:14 kanga kernel: EIP is at journal_bmap_Rbbdc8009 [jbd] 0x58
Apr 25 04:37:14 kanga kernel: eax: 0000001d ebx: 00000000 ecx: c02af5c4
edx: 00001f06
Apr 25 04:37:14 kanga kernel: esi: c3a7f640 edi: 00000000 ebp: c45c5800
esp: c71ffe50
Apr 25 04:37:14 kanga kernel: ds: 0018 es: 0018 ss: 0018
Apr 25 04:37:14 kanga kernel: Process kjournald (pid: 148, stackpage=c71ff000)
Apr 25 04:37:14 kanga kernel: Stack: c88093af 0000025a c45c5800 c88052ff
c45c5800 000014ed c45c5800 c880538b
Apr 25 04:37:14 kanga kernel: c45c5800 c3a7f640 c8802811 c45c5800
c45c58e4 00000000 00000000 00000000
Apr 25 04:37:14 kanga kernel: 00000000 c5583aa0 c20a2960 c0b87640
000000f0 c1498ae0 c033ab9c c019f880
Apr 25 04:37:14 kanga kernel: Call Trace:
[wd:__insmod_wd_O/lib/modules/2.4.9-31/kernel/drivers/net/wd.o_+-228433/96]
__insmod_jbd_S.rodata_L96 [jbd] 0x285f
Apr 25 04:37:14 kanga kernel: Call Trace: [<c88093af>]
__insmod_jbd_S.rodata_L96 [jbd] 0x285f
Apr 25 04:37:14 kanga kernel:
[wd:__insmod_wd_O/lib/modules/2.4.9-31/kernel/drivers/net/wd.o_+-244993/96]
log_wait_commit_R6c342301 [jbd] 0xcf
Apr 25 04:37:14 kanga kernel: [<c88052ff>] log_wait_commit_R6c342301 [jbd]
0xcf
Apr 25 04:37:14 kanga kernel:
[wd:__insmod_wd_O/lib/modules/2.4.9-31/kernel/drivers/net/wd.o_+-244853/96]
journal_bmap_Rbbdc8009 [jbd] 0x7b
Apr 25 04:37:14 kanga kernel: [<c880538b>] journal_bmap_Rbbdc8009 [jbd]
0x7b
Apr 25 04:37:15 kanga kernel:
[wd:__insmod_wd_O/lib/modules/2.4.9-31/kernel/drivers/net/wd.o_+-255983/96]
journal_flushpage_R40b21025 [jbd] 0xa21
Apr 25 04:37:15 kanga kernel: [<c8802811>] journal_flushpage_R40b21025
[jbd] 0xa21
Apr 25 04:37:15 kanga kernel: [do_rw_disk+336/752] do_rw_disk [kernel] 0x150
Apr 25 04:37:15 kanga kernel: [<c019f880>] do_rw_disk [kernel] 0x150
Apr 25 04:37:15 kanga kernel: [schedule+622/960] schedule [kernel] 0x26e
Apr 25 04:37:15 kanga kernel: [<c011317e>] schedule [kernel] 0x26e
Apr 25 04:37:15 kanga kernel:
[wd:__insmod_wd_O/lib/modules/2.4.9-31/kernel/drivers/net/wd.o_+-246213/96]
journal_revoke_R67623458 [jbd] 0x5eb
Apr 25 04:37:15 kanga kernel: [<c8804e3b>] journal_revoke_R67623458 [jbd]
0x5eb
Apr 25 04:37:15 kanga kernel:
[wd:__insmod_wd_O/lib/modules/2.4.9-31/kernel/drivers/net/wd.o_+-246512/96]
journal_revoke_R67623458 [jbd] 0x4c0
Apr 25 04:37:15 kanga kernel: [<c8804d10>] journal_revoke_R67623458 [jbd]
0x4c0
Apr 25 04:37:15 kanga kernel: [kernel_thread+38/48] kernel_thread [kernel] 0x26
Apr 25 04:37:15 kanga kernel: [<c0105726>] kernel_thread [kernel] 0x26
Apr 25 04:37:15 kanga kernel:
[wd:__insmod_wd_O/lib/modules/2.4.9-31/kernel/drivers/net/wd.o_+-246480/96]
journal_revoke_R67623458 [jbd] 0x4e0
Apr 25 04:37:15 kanga kernel: [<c8804d30>] journal_revoke_R67623458 [jbd]
0x4e0
Apr 25 04:37:15 kanga kernel:
Apr 25 04:37:15 kanga kernel:
Apr 25 04:37:15 kanga kernel: Code: 0f 0b 59 58 eb 04 89 f6 89 c3 89 d8 5b c3 8d
76 00 8d bc 27
####################################End of /var/log/messages
##################################
--
.............Tom "Nothing would please me more than being able to
tdiehl@rogueind.com hire ten programmers and deluge the hobby market
with good software." -- Bill Gates 1976
We are still waiting ....
On Apr 30, 2002 21:54 -0400, Tom Diehl wrote:> Hi all, > Sorry for the repost. If I should be asking somewhere else please tell me > where. I woke up a few days ago to find this on one of my machines. > Below is hopefully the revelent output from dmesg and /var/log/messages. I > have had this b4 but this is the first time I have been able to get any > useful information from it. The machine usually locks and all I see is the > failure on the console.It looks like you were getting garbage from the disk before the journal assertion happened (i.e. the ext3 error), and the journal assertion is just there to save your filesystem from getting corrupted with further bad operations.> This is a stock 7.2 system with all revelant updates. > Not sure what other info to provide so if I missed something please let me > know.I would really recommend upgrading to the latest RH errata kernel. The ext3 code has had a number of bugs fixed since 2.4.9. It might also be related to IDE stuff, don't know.> ide1: reset: successWhen did that reset happen? It wasn't in the syslog that you sent.> EXT3-fs error (device ide1(22,65)): ext3_readdir: bad entry in directory #2665467: rec_len % 4 != 0 - offset=0, inode=762621470, rec_len=44574, name_len=110The rec_len is way out. The inode number is probably also bad, but not sure...> Assertion failure in journal_bmap_Rbbdc8009() at journal.c:602: "ret != 0" > kernel BUG at journal.c:602!Just a symptom of bad data, not the real cause. Note that I wanted to look at this bit of code, but that assertion is not even there anymore (the kernel turns the filesystem read only and just returns now). Cheers, Andreas -- Andreas Dilger http://www-mddsp.enel.ucalgary.ca/People/adilger/ http://sourceforge.net/projects/ext2resize/