Raid 0 en sata : kernel bug ?

dg-switcher · Juin 23, 2005, 9:26

yo les gens

j’ai un petit problème avec mon raid 0 en sata sur 2 maxtor go

le raid tombe assez souvent… voilà la trace d’hier soir dans les logs

Jun 22 22:48:06 pcswitcher – MARK –
Jun 22 22:50:31 pcswitcher kernel: attempt to access beyond end of device
Jun 22 22:50:31 pcswitcher kernel: md0: rw=0, want=5123899400, limit=468882944
Jun 22 22:50:31 pcswitcher kernel: ------------[ cut here ]------------
Jun 22 22:50:31 pcswitcher kernel: kernel BUG at %%Ë^\^E!Â^W\^5^U^P^\217^S^\^]S^Q^S^Z^K^OÞ^X`^Nn^Z%%^PÕ^\\233^R0^]Ð^R1^YÓ^NÓ^R^H^A^P2^Fù^Q:651!
Jun 22 22:50:31 pcswitcher kernel: invalid operand: 0000 [#1]
Jun 22 22:50:31 pcswitcher kernel: Modules linked in: nls_iso8859_1 nls_cp437 mousedev tsdev psmouse nvidia parport_pc lp parport ipv6 wlan_wep evdev sata_sil ath_pci ath_rate_onoe wlan ath_hal sata_nv libata snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc forcedeth usb_storage ehci_hcd ohci_hcd usbcore i2c_nforce2 i2c_core sd_mod sr_mod sbp2 scsi_mod ieee1394 ide_cd cdrom rtc ide_disk ide_generic hpt34x hpt366 rz1000 generic sc1200 pdc202xx_old pdc202xx_new opti621 amd74xx unix
Jun 22 22:50:31 pcswitcher kernel: CPU: 0
Jun 22 22:50:31 pcswitcher kernel: EIP: 0060:[reiserfs_allocate_blocks_for_region+3978/4445] Tainted: P VLI
Jun 22 22:50:31 pcswitcher kernel: EFLAGS: 00210246 (2.6.11)
Jun 22 22:50:31 pcswitcher kernel: EIP is at reiserfs_allocate_blocks_for_region+0xf8a/0x115d
Jun 22 22:50:31 pcswitcher kernel: eax: 20000000 ebx: 00000000 ecx: f46d3dbc edx: c108ad60
Jun 22 22:50:31 pcswitcher kernel: esi: dd6d6018 edi: 000003f1 ebp: f08667ac esp: f46d3cf4
Jun 22 22:50:31 pcswitcher kernel: ds: 007b es: 007b ss: 0068
Jun 22 22:50:31 pcswitcher kernel: Process amule (pid: 3845, threadinfo=f46d2000 task=f3dcf560)
Jun 22 22:50:31 pcswitcher kernel: Stack: c0128e3b dfff7560 f0b89200 f0b89200 00000000 c0140e70 00000000 00000000
Jun 22 22:50:31 pcswitcher kernel: dffd4640 dfffef40 00000800 00000000 00000000 00000001 dd6d6030 c2fce0e4
Jun 22 22:50:31 pcswitcher kernel: 0a037000 00000000 c0140d58 dfff7d60 c2fce0b0 c0140c3f c2fce0b0 c10850c0
Jun 22 22:50:31 pcswitcher kernel: Call Trace:
Jun 22 22:50:31 pcswitcher kernel: [mempool_free+81/86] mempool_free+0x51/0x56
Jun 22 22:50:31 pcswitcher kernel: [bio_destructor+52/57] bio_destructor+0x34/0x39
Jun 22 22:50:31 pcswitcher kernel: [free_buffer_head+26/39] free_buffer_head+0x1a/0x27
Jun 22 22:50:31 pcswitcher kernel: [try_to_free_buffers+91/107] try_to_free_buffers+0x5b/0x6b
Jun 22 22:50:31 pcswitcher kernel: [reiserfs_unprepare_pages+35/79] reiserfs_unprepare_pages+0x23/0x4f
Jun 22 22:50:31 pcswitcher kernel: [reiserfs_prepare_file_region_for_write+2111/2126] reiserfs_prepare_file_region_for_write+0x83f/0x84e
Jun 22 22:50:31 pcswitcher kernel: [reiserfs_file_write+1029/1383] reiserfs_file_write+0x405/0x567
Jun 22 22:50:31 pcswitcher kernel: [vfs_statfs64+17/43] vfs_statfs64+0x11/0x2b
Jun 22 22:50:31 pcswitcher kernel: [path_release+12/49] path_release+0xc/0x31
Jun 22 22:50:31 pcswitcher kernel: [sys_statfs64+118/131] sys_statfs64+0x76/0x83
Jun 22 22:50:31 pcswitcher kernel: [vfs_write+156/247] vfs_write+0x9c/0xf7
Jun 22 22:50:31 pcswitcher kernel: [sys_write+59/99] sys_write+0x3b/0x63
Jun 22 22:50:31 pcswitcher kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Jun 22 22:50:31 pcswitcher kernel: Code: ff 58 5a 31 db c7 44 24 30 00 00 00 00 3b 9c 24 5c 01 00 00 0f 8d fc 00 00 00 8b 84 24 64 01 00 00 8b 14 98 8b 02 f6 c4 10 75 02 <0f> 0b 8b 02 8b 7a 0c f6 c4 10 75 02 0f 0b 85 ff 75 14 68 e0 40

quelqu’un a entendu parler d’un bug dans le noyau ou ca serais amule qui fait planter le raid ?

v_atekor · Juin 23, 2005, 10:01

Le bug est dans reiserfs.

Reiser3 n’est pas connu pour sa stabilité, surtout avec les petits indiens
C’est indépendant de amule. Essaie d’utiliser ext3 ?

Envoie le rapport de bug sur la mailing list reiserfs (pour reiser3)

j_c_p_1_1 · Juin 23, 2005, 10:14

C’est quelle version du noyau (pour info) ?