[Bug 206390] New: BUG in ext3fs/namei
https://bugzilla.novell.com/show_bug.cgi?id=206390 Summary: BUG in ext3fs/namei Product: SUSE LINUX 10.0 Version: Final Platform: i686 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: matthias.andree@gmx.de QAContact: qa@suse.de "find" scanning the disk (probably from a find(1) run triggered probably by updatedb or otherwise through cron) causes a kernel "BUG" as quoted below. The exact reason is unknown, I'll try to obtain e2fsprogs logs and follow up should such logs contain any relevant information. Sep 17 14:51:01 merlin kernel: Assertion failure in dx_probe() at fs/ext3/namei.c:381: "dx_get_limit(entries) == dx_root_limit(dir, root->in fo.info_length)" Sep 17 14:51:01 merlin kernel: ------------[ cut here ]------------ Sep 17 14:51:01 merlin kernel: kernel BUG at fs/ext3/namei.c:381! Sep 17 14:51:01 merlin kernel: invalid operand: 0000 [#1] Sep 17 14:51:01 merlin kernel: Modules linked in: hfsplus subfs vmnet vmmon nfsd autofs4 ppdev libafs snd_pcm_oss snd_mixer_oss snd_seq butt on battery ac rfcomm l2cap bluetooth ipt_REJECT ipt_recent ipt_state ipt_TCPMSS iptable_filter ipt_MASQUERADE iptable_nat iptable_mangle ip_ tables nvidia agpgart tun ipv6 ip_conntrack_irc ip_conntrack_ftp ip_conntrack it87 i2c_sensor i2c_isa nls_iso8859_1 nls_cp437 vfat fat xfs e xportfs usbhid usblp bt878 snd_bt87x snd_via82xx gameport snd_ac97_codec via_rhine snd_ac97_bus snd_pcm snd_timer snd_page_alloc snd_mpu401_ uart snd_rawmidi snd_seq_device tuner snd btaudio soundcore tvaudio msp3400 ehci_hcd uhci_hcd bttv usbcore video_buf pci_hotplug i2c_viapro generic firmware_class i2c_algo_bit v4l2_common btcx_risc tveeprom i2c_core videodev dm_mod parport_pc lp parport 3c59x mii ext3 jbd ide_cd fan thermal processor via82cxxx st sr_mod cdrom sg sym53c8xx scsi_transport_spi sata_via libata sd_mod scsi_mod ide_disk ide_core Sep 17 14:51:01 merlin kernel: CPU: 0 Sep 17 14:51:01 merlin kernel: EIP: 0060:[<f8f468fa>] Tainted: P U VLI Sep 17 14:51:01 merlin kernel: EFLAGS: 00010286 (2.6.13-15.12-default) Sep 17 14:51:01 merlin kernel: EIP is at dx_probe+0xea/0x2d0 [ext3] Sep 17 14:51:01 merlin kernel: eax: 00000084 ebx: e8cbe000 ecx: c035322c edx: 00000000 Sep 17 14:51:01 merlin kernel: esi: e8cbe018 edi: c6853b0c ebp: e88d146c esp: c4c17e40 Sep 17 14:51:01 merlin kernel: ds: 007b es: 007b ss: 0068 Sep 17 14:51:01 merlin kernel: Process find (pid: 12401, threadinfo=c4c16000 task=ea28a570) Sep 17 14:51:01 merlin kernel: Stack: f8f53774 f8f5284c f8f55593 0000017d f8f53730 c4c17ea4 00000000 00000000 Sep 17 14:51:01 merlin kernel: f8f55b29 00000002 00000000 00000000 e88d146c 00000000 f8f46db4 c4c17e8c Sep 17 14:51:02 merlin kernel: c4c17eb8 00000000 f343f6a0 00000000 ffffffff 00008000 00000000 00000000 Sep 17 14:51:02 merlin kernel: Call Trace: Sep 17 14:51:02 merlin kernel: [<f8f46db4>] ext3_htree_fill_tree+0x94/0x1c0 [ext3] Sep 17 14:51:02 merlin kernel: [<f8f40f87>] ext3_dx_readdir+0xe7/0x1a0 [ext3] Sep 17 14:51:02 merlin kernel: [<c016a090>] filldir64+0x0/0xd0 Sep 17 14:51:02 merlin kernel: [<c016a090>] filldir64+0x0/0xd0 Sep 17 14:51:02 merlin kernel: [<f8f40a72>] ext3_readdir+0x352/0x490 [ext3] Sep 17 14:51:02 merlin kernel: [<c016a090>] filldir64+0x0/0xd0 Sep 17 14:51:02 merlin kernel: [<c016a090>] filldir64+0x0/0xd0 Sep 17 14:51:02 merlin kernel: [<c0169de9>] vfs_readdir+0x79/0xb0 Sep 17 14:51:02 merlin kernel: [<c016a1c3>] sys_getdents64+0x63/0xa7 Sep 17 14:51:02 merlin kernel: [<c0102d3b>] sysenter_past_esp+0x54/0x79 Sep 17 14:51:02 merlin kernel: Code: 66 8b 16 81 e2 ff ff 00 00 39 c2 74 29 68 30 37 f5 f8 68 7d 01 00 00 68 93 55 f5 f8 68 4c 28 f5 f8 68 7 4 37 f5 f8 e8 56 5f 1d c7 <0f> 0b 7d 01 93 55 f5 f8 83 c4 14 8b 44 24 28 c7 44 24 0c 00 00 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206390 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |matthias.andree@gmx.de ------- Comment #1 from gregkh@novell.com 2006-09-18 07:05 MST ------- Can you verify that this happens on 10.1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206390 matthias.andree@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|matthias.andree@gmx.de | ------- Comment #2 from matthias.andree@gmx.de 2006-09-18 08:43 MST ------- Sorry, no. Apart from running e2fsck (log in separate comment below), I don't have any 10.1 installations here and have no desire to set up one: 10.1 is an administrator nightmare through its sloooooooooow rug and ZLM junk and doesn't provide real added value on top of 10.0 for my situation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206390 ------- Comment #3 from matthias.andree@gmx.de 2006-09-18 08:44 MST ------- This is the output I got from e2fsck -fp $PARTITION: /dev/sda5: HTREE directory inode 211835 has an invalid root node. HTREE INDEX CLEARED. /dev/sda5: 117249/488640 files (13.2% non-contiguous), 889497/975940 blocks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206390 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |matthias.andree@gmx.de ------- Comment #4 from lmb@novell.com 2006-09-19 03:56 MST ------- Ok, so the filesystem was corrupt on disk. a) Can you reproduce this without proprietary/unsupported modules loaded? b) Is memtest OK on said machine? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206390 matthias.andree@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|matthias.andree@gmx.de | ------- Comment #5 from matthias.andree@gmx.de 2006-09-19 06:10 MST ------- a) no, since I ran e2fsck to fix the issue and avoid further crashes b) probably, meaning it was last time I ran it a few months ago (and this machine behaves fine otherwise - which isn't a proof of course), but I can re-run memtest next night if needed. A triggering factor might have been my using an obsolete ext2 driver on an other operating system (multi-boot computer) but still this shouldn't cause BUG()s. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206390 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID ------- Comment #6 from lmb@novell.com 2006-09-19 08:15 MST ------- Filesystems are only 95% robust when it comes to reading possibly corrupted metadata. (Disk failures tend to be more along the lines of EIO, not of returning wrong data.) A BUG() can be expected in such a case, in particular as it can't tell whether it was corrupted in memory or on disk. This will have to be closed as INVALID. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com