* 2.4.17 oops - ext2/ext3 fs corruption (?)
@ 2002-01-05 18:45 Eric
2002-01-05 19:58 ` Andrew Morton
0 siblings, 1 reply; 6+ messages in thread
From: Eric @ 2002-01-05 18:45 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1509 bytes --]
I seem to be having a reoccurring problem with my Red Hat 7.2 system
running kernel 2.4.17. Four times now, I have seen the kernel generate an
oops. After the oops, I find that one of file systems is no longer sane.
The effect that I see is a Segmentation Fault when things like ls or du
some directory (the directory is never the same). Also, when the system
is going down for a reboot, it is unable to umount the file system. The
umount command returns a "bad lseek" error.
The first time this happened, it resulted in catastrophic corruption of
/usr and I had to reinstall. At this time, /usr was an ext2 file system.
When I reinstalled, I took the opportunity to reformat all the file
systems, except /home, as ext3.
The second and third times I saw this problem on my /home (ext2) file
system. Fortunately, there was no corruption of the file system after
rebooting the box. I do not have the oops generated by the kernel when
these events occurred.
The fourth time was on /usr (ext3) and did not result in corruption.
Although, a read-only check of the file system before rebooting showed
files with duplicate blocks. I collected the 2 oops logs I found in dmesg
and ran them through ksymoops. There are quite a few warnings, so I don't
know if they are any good.
I also included dmesg in case that is helpful. If any other information
is required, I would be glad to provide it. Any suggestions on what I
could do to fix the problem would be greatly appreciated.
Thanks,
Eric
[-- Attachment #2: dmesg (no oops) --]
[-- Type: TEXT/PLAIN, Size: 5661 bytes --]
Linux version 2.4.17 (root@dragon.yggdrasil.invalid) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #2 Mon Dec 24 22:23:36 PST 2001
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000c000000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 49152
zone(0): 4096 pages.
zone(1): 45056 pages.
zone(2): 0 pages.
Kernel command line: ro root=/dev/sda1
Initializing CPU#0
Detected 200.458 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 399.76 BogoMIPS
Memory: 191176k/196608k available (1185k kernel code, 5048k reserved, 324k data, 232k init, 0k highmem)
Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: Before vendor init, caps: 000001bf 00000000 00000000, vendor = 0
Intel Pentium with F0 0F bug - workaround enabled.
CPU: After vendor init, caps: 000001bf 00000000 00000000 00000000
CPU: After generic, caps: 000001bf 00000000 00000000 00000000
CPU: Common caps: 000001bf 00000000 00000000 00000000
CPU: Intel Pentium 75 - 200 stepping 0c
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: none
PCI: PCI BIOS revision 2.10 entry at 0xf0430, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7000] at 00:07.0
Limiting direct PCI/PCI transfers.
Activating ISA DMA hang workarounds.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
PCI: Found IRQ 11 for device 00:0c.0
matroxfb: Matrox Millennium II (PCI) detected
matroxfb: MTRR's turned on
matroxfb: 640x480x8bpp (virtual: 640x6553)
matroxfb: framebuffer at 0xE6000000, mapped to 0xcc807000, size 4194304
Console: switching to colour frame buffer device 80x30
fb0: MATROX VGA frame buffer device
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
lp0: using parport0 (polling).
Real Time Clock Driver v1.10e
block: 128 slots per queue, batch=32
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001)
PCI: Found IRQ 12 for device 00:09.0
eth0: Lite-On PNIC-II rev 37 at 0xe000, 00:A0:CC:E4:38:DB, IRQ 12.
SCSI subsystem driver Revision: 1.00
PCI: Found IRQ 10 for device 00:0b.0
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
Vendor: PLEXTOR Model: CD-ROM PX-20TS Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 02
(scsi0:A:3): 10.000MB/s transfers (10.000MHz, offset 15)
Vendor: PLEXTOR Model: CD-R PX-R820T Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
(scsi0:A:4): 10.000MB/s transfers (10.000MHz, offset 8)
Vendor: QUANTUM Model: ATLAS_V__9_WLS Rev: 0230
Type: Direct-Access ANSI SCSI revision: 03
(scsi0:A:6): 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
scsi0:A:6:0: Tagged Queuing enabled. Depth 253
Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
SCSI device sda: 17930694 512-byte hdwr sectors (9181 MB)
Partition check:
sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 >
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 4, lun 0
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.12
sr1: scsi3-mmc drive: 20x/20x writer cd/rw xa/form2 cdda tray
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 232k freed
Adding Swap: 393320k swap-space (priority -1)
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on sd(8,1), internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on sd(8,8), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on sd(8,7), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on sd(8,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on sd(8,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
[-- Attachment #3: oops #1 --]
[-- Type: TEXT/PLAIN, Size: 7425 bytes --]
ksymoops 2.4.1 on i586 2.4.17. Options used
-v /boot/vmlinux-2.4.17 (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.17/ (default)
-m /boot/System.map-2.4.17 (default)
No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Warning (compare_maps): ksyms_base symbol journal_abort_R__ver_journal_abort not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_ack_err_R__ver_journal_ack_err not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_blocks_per_page_R__ver_journal_blocks_per_page not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_bmap_R__ver_journal_bmap not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_check_available_features_R__ver_journal_check_available_features not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_check_used_features_R__ver_journal_check_used_features not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_clear_err_R__ver_journal_clear_err not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_create_R__ver_journal_create not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_destroy_R__ver_journal_destroy not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_dirty_data_R__ver_journal_dirty_data not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_dirty_metadata_R__ver_journal_dirty_metadata not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_errno_R__ver_journal_errno not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_extend_R__ver_journal_extend not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_flush_R__ver_journal_flush not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_flushpage_R__ver_journal_flushpage not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_force_commit_R__ver_journal_force_commit not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_forget_R__ver_journal_forget not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_get_create_access_R__ver_journal_get_create_access not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_get_undo_access_R__ver_journal_get_undo_access not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_get_write_access_R__ver_journal_get_write_access not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_init_dev_R__ver_journal_init_dev not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_init_inode_R__ver_journal_init_inode not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_load_R__ver_journal_load not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_lock_updates_R__ver_journal_lock_updates not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_recover_R__ver_journal_recover not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_restart_R__ver_journal_restart not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_revoke_R__ver_journal_revoke not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_set_features_R__ver_journal_set_features not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_start_R__ver_journal_start not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_stop_R__ver_journal_stop not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_try_start_R__ver_journal_try_start not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_try_to_free_buffers_R__ver_journal_try_to_free_buffers not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_unlock_updates_R__ver_journal_unlock_updates not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_update_format_R__ver_journal_update_format not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_update_superblock_R__ver_journal_update_superblock not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_wipe_R__ver_journal_wipe not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol log_start_commit_R__ver_log_start_commit not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol log_wait_commit_R__ver_log_wait_commit not found in vmlinux. Ignoring ksyms_base entry
Unable to handle kernel paging request at virtual address 3b98e70a
c013ee54
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c013ee54>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010203
eax: c1340000 ebx: 3b98e6fa ecx: 0000000f edx: c2124ec5
esi: c2124ec5 edi: c13ead80 ebp: 3b98e70a esp: c87c1ef8
ds: 0018 es: 0018 ss: 0018
Process updatedb (pid: 5029, stackpage=c87c1000)
Stack: c1366608 cbe53000 c2124ec5 00000007 c87c1f64 cbe53000 c13ead80 c87c1f9c
c0136d40 c131c620 c87c1f64 c87c1f64 c013740a c131c620 c87c1f64 00000000
00000008 cbe53007 00000000 00002b09 00000000 00000000 00001000 fffffff4
Call Trace: [<c0136d40>] [<c013740a>] [<c0136b1f>] [<c01379d3>] [<c0134bb4>]
[<c0106e04>] [<c0106cf3>]
Code: 8b 6d 00 39 53 44 0f 85 90 00 00 00 8b 44 24 24 39 43 0c 0f
>>EIP; c013ee54 <d_lookup+64/120> <=====
Trace; c0136d40 <cached_lookup+10/50>
Trace; c013740a <link_path_walk+4ea/730>
Trace; c0136b1f <getname+5f/a0>
Trace; c01379d3 <__user_walk+33/50>
Trace; c0134bb4 <sys_lstat64+14/70>
Trace; c0106e04 <error_code+34/40>
Trace; c0106cf3 <system_call+33/40>
Code; c013ee54 <d_lookup+64/120>
00000000 <_EIP>:
Code; c013ee54 <d_lookup+64/120> <=====
0: 8b 6d 00 mov 0x0(%ebp),%ebp <=====
Code; c013ee57 <d_lookup+67/120>
3: 39 53 44 cmp %edx,0x44(%ebx)
Code; c013ee5a <d_lookup+6a/120>
6: 0f 85 90 00 00 00 jne 9c <_EIP+0x9c> c013eef0 <d_lookup+100/120>
Code; c013ee60 <d_lookup+70/120>
c: 8b 44 24 24 mov 0x24(%esp,1),%eax
Code; c013ee64 <d_lookup+74/120>
10: 39 43 0c cmp %eax,0xc(%ebx)
Code; c013ee67 <d_lookup+77/120>
13: 0f 00 00 sldt (%eax)
39 warnings issued. Results may not be reliable.
[-- Attachment #4: oops #2 --]
[-- Type: TEXT/PLAIN, Size: 7373 bytes --]
ksymoops 2.4.1 on i586 2.4.17. Options used
-v /boot/vmlinux-2.4.17 (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.17/ (default)
-m /boot/System.map-2.4.17 (default)
No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Warning (compare_maps): ksyms_base symbol journal_abort_R__ver_journal_abort not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_ack_err_R__ver_journal_ack_err not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_blocks_per_page_R__ver_journal_blocks_per_page not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_bmap_R__ver_journal_bmap not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_check_available_features_R__ver_journal_check_available_features not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_check_used_features_R__ver_journal_check_used_features not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_clear_err_R__ver_journal_clear_err not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_create_R__ver_journal_create not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_destroy_R__ver_journal_destroy not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_dirty_data_R__ver_journal_dirty_data not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_dirty_metadata_R__ver_journal_dirty_metadata not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_errno_R__ver_journal_errno not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_extend_R__ver_journal_extend not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_flush_R__ver_journal_flush not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_flushpage_R__ver_journal_flushpage not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_force_commit_R__ver_journal_force_commit not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_forget_R__ver_journal_forget not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_get_create_access_R__ver_journal_get_create_access not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_get_undo_access_R__ver_journal_get_undo_access not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_get_write_access_R__ver_journal_get_write_access not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_init_dev_R__ver_journal_init_dev not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_init_inode_R__ver_journal_init_inode not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_load_R__ver_journal_load not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_lock_updates_R__ver_journal_lock_updates not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_recover_R__ver_journal_recover not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_restart_R__ver_journal_restart not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_revoke_R__ver_journal_revoke not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_set_features_R__ver_journal_set_features not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_start_R__ver_journal_start not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_stop_R__ver_journal_stop not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_try_start_R__ver_journal_try_start not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_try_to_free_buffers_R__ver_journal_try_to_free_buffers not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_unlock_updates_R__ver_journal_unlock_updates not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_update_format_R__ver_journal_update_format not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_update_superblock_R__ver_journal_update_superblock not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol journal_wipe_R__ver_journal_wipe not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol log_start_commit_R__ver_log_start_commit not found in vmlinux. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol log_wait_commit_R__ver_log_wait_commit not found in vmlinux. Ignoring ksyms_base entry
<1>Unable to handle kernel paging request at virtual address bbf3c2ff
c013ee54
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c013ee54>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010283
eax: c1340000 ebx: bbf3c2ef ecx: 0000000f edx: f8d71b6c
esi: f8d71b6c edi: c611b660 ebp: bbf3c2ff esp: c4a41ef8
ds: 0018 es: 0018 ss: 0018
Process ls (pid: 5759, stackpage=c4a41000)
Stack: c1366608 c9eaa020 f8d71b6c 0000000b c4a41f64 c9eaa020 c611b660 c4a41f9c
c0136d40 c612ec40 c4a41f64 c4a41f64 c013740a c612ec40 c4a41f64 00000000
00000008 c9eaa02b 00000000 00000000 00000000 00000000 000006c0 fffffff4
Call Trace: [<c0136d40>] [<c013740a>] [<c0136b1f>] [<c01379d3>] [<c0134bb4>]
[<c0106cf3>]
Code: 8b 6d 00 39 53 44 0f 85 90 00 00 00 8b 44 24 24 39 43 0c 0f
>>EIP; c013ee54 <d_lookup+64/120> <=====
Trace; c0136d40 <cached_lookup+10/50>
Trace; c013740a <link_path_walk+4ea/730>
Trace; c0136b1f <getname+5f/a0>
Trace; c01379d3 <__user_walk+33/50>
Trace; c0134bb4 <sys_lstat64+14/70>
Trace; c0106cf3 <system_call+33/40>
Code; c013ee54 <d_lookup+64/120>
00000000 <_EIP>:
Code; c013ee54 <d_lookup+64/120> <=====
0: 8b 6d 00 mov 0x0(%ebp),%ebp <=====
Code; c013ee57 <d_lookup+67/120>
3: 39 53 44 cmp %edx,0x44(%ebx)
Code; c013ee5a <d_lookup+6a/120>
6: 0f 85 90 00 00 00 jne 9c <_EIP+0x9c> c013eef0 <d_lookup+100/120>
Code; c013ee60 <d_lookup+70/120>
c: 8b 44 24 24 mov 0x24(%esp,1),%eax
Code; c013ee64 <d_lookup+74/120>
10: 39 43 0c cmp %eax,0xc(%ebx)
Code; c013ee67 <d_lookup+77/120>
13: 0f 00 00 sldt (%eax)
39 warnings issued. Results may not be reliable.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.4.17 oops - ext2/ext3 fs corruption (?)
2002-01-05 18:45 2.4.17 oops - ext2/ext3 fs corruption (?) Eric
@ 2002-01-05 19:58 ` Andrew Morton
2002-01-05 23:31 ` Eric
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Morton @ 2002-01-05 19:58 UTC (permalink / raw)
To: Eric; +Cc: linux-kernel
Eric wrote:
>
> I seem to be having a reoccurring problem with my Red Hat 7.2 system
> running kernel 2.4.17. Four times now, I have seen the kernel generate an
> oops. After the oops, I find that one of file systems is no longer sane.
> The effect that I see is a Segmentation Fault when things like ls or du
> some directory (the directory is never the same). Also, when the system
> is going down for a reboot, it is unable to umount the file system. The
> umount command returns a "bad lseek" error.
>
> The first time this happened, it resulted in catastrophic corruption of
> /usr and I had to reinstall. At this time, /usr was an ext2 file system.
> When I reinstalled, I took the opportunity to reformat all the file
> systems, except /home, as ext3.
>
Everything here points at failing hardware. Probably memory errors.
People say that memtest86 is good at detecting these things. Another
way to verify this is to move the same setup onto a different computer...
-
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.4.17 oops - ext2/ext3 fs corruption (?)
2002-01-05 19:58 ` Andrew Morton
@ 2002-01-05 23:31 ` Eric
2002-01-06 10:15 ` Daniel Phillips
0 siblings, 1 reply; 6+ messages in thread
From: Eric @ 2002-01-05 23:31 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Sat, 5 Jan 2002, Andrew Morton wrote:
> Eric wrote:
> >
> > I seem to be having a reoccurring problem with my Red Hat 7.2 system
> > running kernel 2.4.17. Four times now, I have seen the kernel generate an
> > oops. After the oops, I find that one of file systems is no longer sane.
> > The effect that I see is a Segmentation Fault when things like ls or du
> > some directory (the directory is never the same). Also, when the system
> > is going down for a reboot, it is unable to umount the file system. The
> > umount command returns a "bad lseek" error.
>
> Everything here points at failing hardware. Probably memory errors.
> People say that memtest86 is good at detecting these things. Another
> way to verify this is to move the same setup onto a different computer...
I ran memtest86 on the system and let it complete 4 passes before I
stopped it. It found no errors. Unfortunately, I do not have another
system available to test this on. Are there any other diagnostics I can
run to determine if this is truly a hardware problem?
Thanks,
Eric
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.4.17 oops - ext2/ext3 fs corruption (?)
2002-01-05 23:31 ` Eric
@ 2002-01-06 10:15 ` Daniel Phillips
2002-01-12 14:25 ` Eric
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Phillips @ 2002-01-06 10:15 UTC (permalink / raw)
To: Eric, Andrew Morton; +Cc: linux-kernel
On January 6, 2002 12:31 am, Eric wrote:
> On Sat, 5 Jan 2002, Andrew Morton wrote:
> > Eric wrote:
> > >
> > > I seem to be having a reoccurring problem with my Red Hat 7.2 system
> > > running kernel 2.4.17. Four times now, I have seen the kernel generate an
> > > oops. After the oops, I find that one of file systems is no longer sane.
> > > The effect that I see is a Segmentation Fault when things like ls or du
> > > some directory (the directory is never the same). Also, when the system
> > > is going down for a reboot, it is unable to umount the file system. The
> > > umount command returns a "bad lseek" error.
> >
> > Everything here points at failing hardware. Probably memory errors.
> > People say that memtest86 is good at detecting these things. Another
> > way to verify this is to move the same setup onto a different computer...
>
> I ran memtest86 on the system and let it complete 4 passes before I
> stopped it. It found no errors. Unfortunately, I do not have another
> system available to test this on. Are there any other diagnostics I can
> run to determine if this is truly a hardware problem?
This doesn't smell like hardware to me, since your two backtraces are identical:
>>EIP; c013ee54 <d_lookup+64/120> <=====
Trace; c0136d40 <cached_lookup+10/50>
Trace; c013740a <link_path_walk+4ea/730>
Trace; c0136b1f <getname+5f/a0>
Trace; c01379d3 <__user_walk+33/50>
Trace; c0134bb4 <sys_lstat64+14/70>
Trace; c0106e04 <error_code+34/40>
Trace; c0106cf3 <system_call+33/40>
Code; c013ee54 <d_lookup+64/120>
00000000 <_EIP>:
Code; c013ee54 <d_lookup+64/120> <=====
0: 8b 6d 00 mov 0x0(%ebp),%ebp <=====
Code; c013ee57 <d_lookup+67/120>
3: 39 53 44 cmp %edx,0x44(%ebx)
Code; c013ee5a <d_lookup+6a/120>
6: 0f 85 90 00 00 00 jne 9c <_EIP+0x9c> c013eef0 <d_lookup+100/120>
Code; c013ee60 <d_lookup+70/120>
c: 8b 44 24 24 mov 0x24(%esp,1),%eax
Code; c013ee64 <d_lookup+74/120>
10: 39 43 0c cmp %eax,0xc(%ebx)
Code; c013ee67 <d_lookup+77/120>
13: 0f 00 00 sldt (%eax)
--
Daniel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.4.17 oops - ext2/ext3 fs corruption (?)
2002-01-06 10:15 ` Daniel Phillips
@ 2002-01-12 14:25 ` Eric
2002-01-12 14:52 ` Marco Casaroli
0 siblings, 1 reply; 6+ messages in thread
From: Eric @ 2002-01-12 14:25 UTC (permalink / raw)
To: linux-kernel
On Sun, 6 Jan 2002, Daniel Phillips wrote:
> On January 6, 2002 12:31 am, Eric wrote:
> > On Sat, 5 Jan 2002, Andrew Morton wrote:
> > > Eric wrote:
> > > >
> > > > I seem to be having a reoccurring problem with my Red Hat 7.2 system
> > > > running kernel 2.4.17. Four times now, I have seen the kernel generate an
> > > > oops. After the oops, I find that one of file systems is no longer sane.
> > > > The effect that I see is a Segmentation Fault when things like ls or du
> > > > some directory (the directory is never the same). Also, when the system
> > > > is going down for a reboot, it is unable to umount the file system. The
> > > > umount command returns a "bad lseek" error.
> > >
> > > Everything here points at failing hardware. Probably memory errors.
> > > People say that memtest86 is good at detecting these things. Another
> > > way to verify this is to move the same setup onto a different computer...
> >
> > I ran memtest86 on the system and let it complete 4 passes before I
> > stopped it. It found no errors. Unfortunately, I do not have another
> > system available to test this on. Are there any other diagnostics I can
> > run to determine if this is truly a hardware problem?
>
> This doesn't smell like hardware to me, since your two backtraces are identical:
In an attempt to try a get more information about what is going on, I
tried compiling a new kernel with the options CONFIG_DEBUG_KERNEL and
CONFIG_DEBUG_BUGVERBOSE turned on. However, this seems to have made
things worse. Now, in about 6-12 hours from boot-up, the system will hang
completely with no information from the kernel on the console. The only
way to get out it is to use the reset button on the front of the box.
Is there anything else I can do to try and determine if this is a kernel
problem? Or at least get more information about what is going on?
Thanks,
Eric
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Re: 2.4.17 oops - ext2/ext3 fs corruption (?)
2002-01-12 14:25 ` Eric
@ 2002-01-12 14:52 ` Marco Casaroli
0 siblings, 0 replies; 6+ messages in thread
From: Marco Casaroli @ 2002-01-12 14:52 UTC (permalink / raw)
To: linux-kernel
> On Sun, 6 Jan 2002, Daniel Phillips wrote:
>
> > On January 6, 2002 12:31 am, Eric wrote:
> > > On Sat, 5 Jan 2002, Andrew Morton wrote:
> > > > Eric wrote:
> > > > >
> > > > > I seem to be having a reoccurring problem with my Red Hat 7.2 system
> > > > > running kernel 2.4.17. Four times now, I have seen the kernel generate an
> > > > > oops. After the oops, I find that one of file systems is no longer sane.
> > > > > The effect that I see is a Segmentation Fault when things like ls or du
> > > > > some directory (the directory is never the same). Also, when the system
> > > > > is going down for a reboot, it is unable to umount the file system. The
> > > > > umount command returns a "bad lseek" error.
> > > >
> > > > Everything here points at failing hardware. Probably memory errors.
> > > > People say that memtest86 is good at detecting these things. Another
> > > > way to verify this is to move the same setup onto a different computer...
> > >
> > > I ran memtest86 on the system and let it complete 4 passes before I
> > > stopped it. It found no errors. Unfortunately, I do not have another
> > > system available to test this on. Are there any other diagnostics I can
> > > run to determine if this is truly a hardware problem?
> >
> > This doesn't smell like hardware to me, since your two backtraces are identical:
>
> In an attempt to try a get more information about what is going on, I
> tried compiling a new kernel with the options CONFIG_DEBUG_KERNEL and
> CONFIG_DEBUG_BUGVERBOSE turned on. However, this seems to have made
> things worse. Now, in about 6-12 hours from boot-up, the system will hang
> completely with no information from the kernel on the console. The only
> way to get out it is to use the reset button on the front of the box.
>
> Is there anything else I can do to try and determine if this is a kernel
> problem? Or at least get more information about what is going on?
>
> Thanks,
>
> Eric
I had the same problem with ext3fs
The problem was when trying to READ from the partition and not when trying to write. That was interesting.
I copied a lot of files to my ext3 partition (5 gig) and when I tried to copy it back to the other partition(vfat) there were some input-output errors and i got all the data lost, I had to format the ext3 partition and install linux again.
So, the problem does not seem to be hardware problem.
I am traveling now, not in my house, so I can't test it one more time, and when I'll be back probably there will be a fixed kernel, but if not, I'll test it again anyway.
Marco
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2002-01-12 14:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-05 18:45 2.4.17 oops - ext2/ext3 fs corruption (?) Eric
2002-01-05 19:58 ` Andrew Morton
2002-01-05 23:31 ` Eric
2002-01-06 10:15 ` Daniel Phillips
2002-01-12 14:25 ` Eric
2002-01-12 14:52 ` Marco Casaroli
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox