XFS a pad kernelu

[Martin Majkus]

Zdravim,

mam IBM xSeries 235 s ServeRaid 6i, kde bezi Debian Woody s kernelem 
2.6.12.4. Filesystem pro data je pouzit XFS. Nedavno se mi stalo 
nasledujici:

1] uzivatele pristupujici z Win pres sambu ke svym diskum zpozorovali 
vyrazne zpomaleni a "kousani" pristupu na disk nasdileny z tohoto serveru.
2] Po chvili (pry cca 5 minut) doslo padu jadra, viz. vypis nize ze 
syslogu (stroj odpovidal na ping, na otevrene porty se slo connectnout, 
ale jinak nic).

Typuji, ze:
a] je vadny HW (ale jiz se to neopakuje)
b] je potreba upgrade firmwaru SCSI radice, viz. archiv a dotaz s 
subjectem "ips.o ve 2.6 kernelu versus upgrade firmwaru serveraidu"
c] je chyba v jadre

Mate s tim nekdo zkusenosti? Kde myslite, ze by mohl byt problem?

Diky za radu.
--
	Martin Majkus

Aug 11 18:46:59 trinity kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 00000004
Aug 11 18:46:59 trinity kernel:  printing eip:
Aug 11 18:46:59 trinity kernel: c02133ba
Aug 11 18:46:59 trinity kernel: *pde = 00000000
Aug 11 18:46:59 trinity kernel: Oops: 0002 [#1]
Aug 11 18:46:59 trinity kernel: SMP
Aug 11 18:46:59 trinity kernel: Modules linked in:
Aug 11 18:46:59 trinity kernel: CPU:    0
Aug 11 18:46:59 trinity kernel: EIP:    0060:[xfs_ail_insert+138/208] 
  Not tainted VLI
Aug 11 18:46:59 trinity kernel: EFLAGS: 00010286   (2.6.12.4)
Aug 11 18:46:59 trinity kernel: EIP is at xfs_ail_insert+0x8a/0xd0
Aug 11 18:46:59 trinity kernel: eax: 00000000   ebx: 00000000   ecx: 
00000000   edx: c37fa8fc
Aug 11 18:46:59 trinity kernel: esi: fffffc19   edi: ffffffff   ebp: 
c262d050   esp: c1be5e08
Aug 11 18:46:59 trinity kernel: ds: 007b   es: 007b   ss: 0068
Aug 11 18:46:59 trinity kernel: Process xfslogd/0 (pid: 76, 
threadinfo=c1be4000 task=c1b43020)
Aug 11 18:46:59 trinity kernel: Stack: 00000000 00000000 f7db0000 
c37fa8fc f7db0018 e4f4c30c c021315e f7db0018
Aug 11 18:46:59 trinity kernel:        c37fa8fc 00000000 000003cc 
00000132 00000132 000003e7 00000000 c37fa8fc
Aug 11 18:46:59 trinity kernel:        c0212d12 f7db0000 c37fa8fc 
000003cc 00000132 00000000 00000001 f7db0000
Aug 11 18:46:59 trinity kernel: Call Trace:
Aug 11 18:46:59 trinity kernel:  [xfs_trans_update_ail+94/176] 
xfs_trans_update_ail+0x5e/0xb0
Aug 11 18:46:59 trinity kernel:  [xfs_trans_chunk_committed+290/464] 
xfs_trans_chunk_committed+0x122/0x1d0
Aug 11 18:46:59 trinity kernel:  [xfs_trans_committed+64/224] 
xfs_trans_committed+0x40/0xe0
Aug 11 18:46:59 trinity kernel:  [xlog_state_do_callback+350/672] 
xlog_state_do_callback+0x15e/0x2a0
Aug 11 18:46:59 trinity kernel:  [xlog_state_done_syncing+84/112] 
xlog_state_done_syncing+0x54/0x70
Aug 11 18:46:59 trinity kernel:  [xlog_iodone+121/176] xlog_iodone+0x79/0xb0
Aug 11 18:46:59 trinity kernel:  [pagebuf_iodone_work+21/80] 
pagebuf_iodone_work+0x15/0x50
Aug 11 18:46:59 trinity kernel:  [remove_wait_queue+15/64] 
remove_wait_queue+0xf/0x40
Aug 11 18:46:59 trinity kernel:  [worker_thread+494/592] 
worker_thread+0x1ee/0x250
Aug 11 18:46:59 trinity kernel:  [pagebuf_iodone_work+0/80] 
pagebuf_iodone_work+0x0/0x50
Aug 11 18:46:59 trinity kernel:  [default_wake_function+0/32] 
default_wake_function+0x0/0x20
Aug 11 18:46:59 trinity kernel:  [default_wake_function+0/32] 
default_wake_function+0x0/0x20
Aug 11 18:46:59 trinity kernel:  [worker_thread+0/592] 
worker_thread+0x0/0x250
Aug 11 18:46:59 trinity kernel:  [kthread+166/176] kthread+0xa6/0xb0
Aug 11 18:46:59 trinity kernel:  [kthread+0/176] kthread+0x0/0xb0
Aug 11 18:46:59 trinity kernel:  [kernel_thread_helper+5/24] 
kernel_thread_helper+0x5/0x18
Aug 11 18:46:59 trinity kernel: Code: ff 89 f0 89 fa 85 d2 7e 08 8b 6d 
04 eb b3 8d 76 00 85 d2 78 05 83 f8 00 77 ef 8b 45 00 8b 54 24 20 89 02 
89 6a 04 89 55
00 8b 02 <89> 50 04 83 c4 08 5b 5e 5f 5d c3 31 c0 31 d2 39 34 24 74 c6 39