Ulrik S. Kofod sagde:
I was just extracting a 96MB tar file ( tar -xWf backup.tar ), the cpu load was 99%
for a long time. I then stopped it and tried again, but this time this popped up in
my ssh session:
--
Message from syslogd@rock at Sat Feb 18 00:47:05 2006 ...
rock kernel: Assertion failure in __journal_unfile_buffer() at
fs/jbd/transaction.c:1520: "jh->b_jlist < 9"
--
A kernel panic dump is displayed on the servers monitor. Here is what I can
remember:
Call trace: jurnal_commit_transaction+<something> [jdb]
Is the panic dump stored anywhere?
When I rebooted, the raid set was dirty and it was re-synced, it did not mark a
drive faulty or started using a spare, the raid set still uses the same two disks
and now everything seems normal, except this is the second time it does this.
It is a fresh install of Cent-OS 4.2 from the DVD image and with the latest updates
from yum.
The server has 4 80GB software mirrored IDE disks, 2 + 2 spares, one on each channel
of a HPT374 controller.
I have no idea about what to look for; I have tested the disks many times with the
vendor tools and no errors have been found.
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
OK I found the panic in /var/log/messages don't know if this makes sense to anybody :)
--
Feb 18 00:47:05 rock kernel: Assertion failure in __journal_unfile_buffer() at
fs/jbd/transaction.c:1520: "jh->b_jlist < 9"
Feb 18 00:47:05 rock kernel: ------------[ cut here ]------------
Feb 18 00:47:05 rock kernel: kernel BUG at fs/jbd/transaction.c:1520!
Feb 18 00:47:05 rock kernel: invalid operand: 0000 [#1]
Feb 18 00:47:05 rock kernel: Modules linked in: md5 ipv6 sunrpc ipt_LOG ipt_recent
ipt_state ip_conntrack iptable_filter ip_t
ables dm_mirror dm_mod button battery ac uhci_hcd 3c59x mii floppy ext3 jbd raid1
Feb 18 00:47:05 rock kernel: CPU: 0
Feb 18 00:47:05 rock kernel: EIP: 0060:[<f884a722>] Not tainted VLI
Feb 18 00:47:05 rock kernel: EFLAGS: 00010212 (2.6.9-22.0.2.EL)
Feb 18 00:47:05 rock kernel: EIP is at __journal_unfile_buffer+0x64/0x14f [jbd]
Feb 18 00:47:05 rock kernel: eax: 00000062 ebx: f45d8aa0 ecx: f8852e0a edx:
f6310dc0
Feb 18 00:47:05 rock kernel: esi: e55295fc edi: 00000000 ebp: e39cdd14 esp:
f6310dbc
Feb 18 00:47:05 rock kernel: ds: 007b es: 007b ss: 0068
Feb 18 00:47:05 rock kernel: Process kjournald (pid: 1396, threadinfo=f6310000
task=f6668210)
Feb 18 00:47:05 rock kernel: Stack: f8852e0a f8852a63 f8852dce 000005f0 f885331b
e39cdd14 c1966200 e55295fc
Feb 18 00:47:05 rock kernel: c1966200 f884bf22 00000000 00000000 00000000
00000000 00000007 ece5e38c
Feb 18 00:47:05 rock kernel: f45d8aa0 ece5e3bc 00001681 00000000 00000000
00000000 00000000 00000000
Feb 18 00:47:06 rock kernel: Call Trace:
Feb 18 00:47:06 rock kernel: [<f884bf22>] journal_commit_transaction+0x6ae/0x1bb8
[jbd]
Feb 18 00:47:06 rock kernel: [<f884fa83>] kjournald+0x179/0x4a1 [jbd]
Feb 18 00:47:06 rock kernel: [<c011e593>] autoremove_wake_function+0x0/0x2d
Feb 18 00:47:06 rock kernel: [<c011e593>] autoremove_wake_function+0x0/0x2d
Feb 18 00:47:06 rock kernel: [<f884f904>] commit_timeout+0x0/0x5 [jbd]
Feb 18 00:47:06 rock kernel: [<f884f90a>] kjournald+0x0/0x4a1 [jbd]
Feb 18 00:47:06 rock kernel: [<c01041d9>] kernel_thread_helper+0x5/0xb
Feb 18 00:47:07 rock kernel: Code: f8 83 c4 14 83 7e 08 08 8b 5e 14 76 29 68 1b 33
85 f8 68 f0 05 00 00 68 ce 2d 85 f8 68 63
2a 85 f8 68 0a 2e 85 f8 e8 d7 6e 8d c7 <0f> 0b f0 05 ce 2d 85 f8 83 c4 14 83 7e 08
00 74 2d 85 db 75 29
Feb 18 00:47:07 rock kernel: <0>Fatal exception: panic in 5 seconds
