Hello all,
I don't really know where to send this, I didn't reach the maintainer of
UFS and I didn't find any linux-fs mailing lists. I hope this isn't too
off-topic.
-- MfG, Jonas Jochum -- Quote of the day: '---------- Forwarded message ---------- Date: Wed, 29 Dec 1999 18:14:57 +0000 (Local time zone must be set--see zic manual page) From: Jonas Jochum <jonas@jonas-jochum.de> Reply-To: jonas.jochum@gmx.de To: daniel.pirkl@email.cz Subject: problems with UFS
Hi,
I just found this in my log files:
-8< --------------------------------------------------------------------
Dec 29 02:00:07 mahatma kernel: 03:0e: rw=0, want=8, limit=0 Dec 29 02:00:21 mahatma kernel: UFS-fs error (device 03:41): ufs_read_inode: inode 309504 has zero nlink Dec 29 02:00:21 mahatma kernel: Dec 29 02:00:21 mahatma kernel: init_special_inode: bogus imode (0) Dec 29 02:00:21 mahatma kernel: attempt to access beyond end of device Dec 29 02:00:21 mahatma kernel: 03:41: rw=0, want=206668419, limit=2062336 Dec 29 02:00:21 mahatma kernel: attempt to access beyond end of device Dec 29 02:00:21 mahatma kernel: 03:41: rw=0, want=206668420, limit=2062336 Dec 29 02:00:21 mahatma kernel: attempt to access beyond end of device Dec 29 02:00:21 mahatma kernel: 03:41: rw=0, want=206668421, limit=2062336 Dec 29 02:00:21 mahatma kernel: attempt to access beyond end of device Dec 29 02:00:21 mahatma kernel: 03:41: rw=0, want=206668422, limit=2062336 Dec 29 02:00:21 mahatma kernel: init_special_inode: bogus imode (31332) Dec 29 02:00:21 mahatma kernel: UFS-fs error (device 03:41): ufs_read_inode: inode 428738 has zero nlink Dec 29 02:00:21 mahatma kernel: Dec 29 02:00:21 mahatma kernel: UFS-fs error (device 03:41): ufs_read_inode: inode 128073 has zero nlink Dec 29 02:00:21 mahatma kernel: Dec 29 02:00:21 mahatma kernel: init_special_inode: bogus imode (0) Dec 29 02:00:21 mahatma kernel: UFS-fs error (device 03:41): ufs_read_inode: inode 421691 has zero nlink Dec 29 02:00:21 mahatma kernel: Dec 29 02:00:21 mahatma kernel: init_special_inode: bogus imode (0) Dec 29 02:00:21 mahatma kernel: init_special_inode: bogus imode (32307) Dec 29 02:00:21 mahatma kernel: init_special_inode: bogus imode (35564) Dec 29 02:00:46 mahatma kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000009c Dec 29 02:00:46 mahatma kernel: printing eip: Dec 29 02:00:46 mahatma kernel: c0173b18 Dec 29 02:00:46 mahatma kernel: *pde = 00000000 Dec 29 02:00:46 mahatma kernel: Oops: 0000 Dec 29 02:00:46 mahatma kernel: CPU: 0 Dec 29 02:00:46 mahatma kernel: EIP: 0010:[ufs_read_cylinder+56/568] Dec 29 02:00:46 mahatma kernel: EFLAGS: 00010292 Dec 29 02:00:46 mahatma kernel: eax: 00000000 ebx: 00000000 ecx: 00000027 edx: 00138000 Dec 29 02:00:46 mahatma kernel: esi: c8d95200 edi: c8d95600 ebp: c8d95600 esp: c1ee3eb4 Dec 29 02:00:46 mahatma kernel: ds: 0018 es: 0018 ss: 0018 Dec 29 02:00:46 mahatma kernel: Process umount (pid: 580, stackpage=c1ee3000) Dec 29 02:00:46 mahatma kernel: Stack: 00000027 c8d95600 0000044c 00000000 c0173fbd c8d95600 00000027 00000000 Dec 29 02:00:46 mahatma kernel: cad5c320 c8d95600 0004b900 00000027 00000002 c8d956e0 00000000 c01746c3 Dec 29 02:00:46 mahatma kernel: c8d95600 00000027 cad5c320 c01768e4 00000000 fffffffe 00000000 00000000 Dec 29 02:00:46 mahatma kernel: Call Trace: [ufs_load_cylinder+445/464] [ufs_free_inode+195/892] [ufs_delete_inode+0/108] [ufs_delete_inode+59/108] [ufs_delete_inode+97/108] [iput+155/496] [shrink_dcache_sb+210/296] Dec 29 02:00:46 mahatma kernel: [do_umount+93/300] [umount_dev+159/292] [sys_umount+178/192] [sys_oldumount+12/16] [system_call+52/64] Dec 29 02:00:46 mahatma kernel: Code: 8b 04 88 8b 68 34 8b 46 3c 83 f0 ff 21 c8 0f af 46 38 31 c9
---------------------------------------------------------------------->8--
cat /proc/version Linux version 2.3.35 (root@mahatma) (gcc version 2.95.2 19991024 (release)) #9 Sun Dec 26 13:41:54 1999
cat /proc/filesystems ext2 msdos vfat nodev proc nodev nfs iso9660 ufs nodev autofs nodev devpts
sh /usr/src/linux/scripts/ver_linux Kernel modules 2.3.9 Gnu C 2.95.2 Binutils 2.9.5.0.22 Linux C Library 2.1.2 Dynamic linker ldd (GNU libc) 2.1.2 Procps 2.0.6 Mount 2.10d Net-tools 1.53 Kbd 0.99 Sh-utils 2.0 Modules Loaded
This shouldn't be of any importance, but here it is: fdisk -l /dev/hda Disk /dev/hda: 255 heads, 63 sectors, 1869 cylinders Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System /dev/hda1 1 90 722893+ a5 BSD/386 /dev/hda2 * 91 103 104422+ 83 Linux /dev/hda3 104 135 257040 c Win95 FAT32 (LBA) /dev/hda4 136 1869 13928355 5 Extended /dev/hda5 136 199 514048+ 83 Linux /dev/hda6 200 276 618471 83 Linux /dev/hda7 277 327 409626 83 Linux /dev/hda8 328 1092 6144831 83 Linux /dev/hda9 1093 1118 208813+ 82 Linux swap /dev/hda10 1119 1373 2048256 b Win95 FAT32 /dev/hda11 1374 1869 3984088+ 83 Linux
fdisk -l /dev/hdb Disk /dev/hdb: 64 heads, 63 sectors, 1023 cylinders Units = cylinders of 4032 * 512 bytes
Device Boot Start End Blocks Id System /dev/hdb1 * 1 1023 2062336+ a5 BSD/386
ksymoops:
Options used: -V (default) -o /lib/modules/2.3.35/ (default) -k /proc/ksyms (default) -l /proc/modules (default) -m /usr/src/linux/System.map (default) -c 1 (default)
You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options.
No modules in ksyms, skipping objects Warning, no symbols in lsmod, is /proc/modules a valid lsmod file? Dec 29 02:00:46 mahatma kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000009c Dec 29 02:00:46 mahatma kernel: c0173b18 Dec 29 02:00:46 mahatma kernel: *pde = 00000000 Dec 29 02:00:46 mahatma kernel: Oops: 0000 Dec 29 02:00:46 mahatma kernel: CPU: 0 Dec 29 02:00:46 mahatma kernel: EIP: 0010:[ufs_read_cylinder+56/568] Dec 29 02:00:46 mahatma kernel: EFLAGS: 00010292 Dec 29 02:00:46 mahatma kernel: eax: 00000000 ebx: 00000000 ecx: 00000027 edx: 00138000 Dec 29 02:00:46 mahatma kernel: esi: c8d95200 edi: c8d95600 ebp: c8d95600 esp: c1ee3eb4 Dec 29 02:00:46 mahatma kernel: ds: 0018 es: 0018 ss: 0018 Dec 29 02:00:46 mahatma kernel: Process umount (pid: 580, stackpage=c1ee3000) Dec 29 02:00:46 mahatma kernel: Stack: 00000027 c8d95600 0000044c 00000000 c0173fbd c8d95600 00000027 00000000 Dec 29 02:00:46 mahatma kernel: cad5c320 c8d95600 0004b900 00000027 00000002 c8d956e0 00000000 c01746c3 Dec 29 02:00:46 mahatma kernel: c8d95600 00000027 cad5c320 c01768e4 00000000 fffffffe 00000000 00000000 Dec 29 02:00:46 mahatma kernel: Call Trace: [ufs_load_cylinder+445/464] [ufs_free_inode+195/892] [ufs_delete_inode+0/108] [ufs_delete_inode+59/108] [ufs_delete_inode+97/108] [iput+155/496] [shrink_dcache_sb+210/296] Dec 29 02:00:46 mahatma kernel: Code: 8b 04 88 8b 68 34 8b 46 3c 83 f0 ff 21 c8 0f af 46 38 31 c9
Code: 00000000 Before first symbol 00000000 <_IP>: <=== Code: 00000000 Before first symbol 0: 8b 04 88 mov (%eax,%ecx,4),%eax <=== Code: 00000003 Before first symbol 3: 8b 68 34 mov 0x34(%eax),%ebp Code: 00000006 Before first symbol 6: 8b 46 3c mov 0x3c(%esi),%eax Code: 00000009 Before first symbol 9: 83 f0 ff xor $0xffffffff,%eax Code: 0000000c Before first symbol c: 21 c8 and %ecx,%eax Code: 0000000e Before first symbol e: 0f af 46 38 imul 0x38(%esi),%eax Code: 00000012 Before first symbol 12: 31 c9 xor %ecx,%ecx
2 warnings issued. Results may not be reliable.
The only thing I did was listing a directory on a ufs partition. When I did that, mount segfaulted. After that, _all_ mounts failed, no matter which filesystem was used. There are still two stuck mounts: root@mahatma:~ # ps x | grep mount 581 tty3 D 0:00 umount /mnt 648 tty1 D 0:00 mount /dev/sr0 /cdrom
I know, that UFS is marked experimental, but I didn't think that it is _that_ experimental. Is there anything I can do to help finding the problem?
-- MfG, Jonas Jochum
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:16 EST