xfs
[Top] [All Lists]

probably useless XFS crash report

To: linux-xfs@xxxxxxxxxxx
Subject: probably useless XFS crash report
From: Derek Glidden <dglidden@xxxxxxxxxxxxxxx>
Date: Thu, 15 Jul 2004 22:01:46 -0400
Sender: linux-xfs-bounce@xxxxxxxxxxx

Gentoo (yeah, yeah. I built the kernel myself anyway) 2.4.26 kernel on an older Dual-Celeron with IDE. Trying to reboot after crashing the box, XFS barfs when it tries to recover the root filesystem. 2.6.7 successfully rebooted and mounted the filesystem. I haven't run xfs_check or anything on the disk because it's a single-disk crash-it box and I haven't had a chance to plug anything else into it so I can boot without booting off the root filesystem. It appears to be working OK, though, after automatic recovery.

I realize this isn't a complete decode, but since it was on the root filesystem it's all I could get from the machine, so if this is useless, please just ignore it. I haven't had any sort of XFS crash for literally years though, so I wanted to report what I could.


ksymoops 2.4.9 on i686 2.4.26-gentoo-r3.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.26-gentoo-r3/ (default)
     -m /boot/System.map-2.4.26-r3 (specified)

cpu: 0, clocks: 1002264, slice: 334088
cpu: 1, clocks: 1002264, slice: 334088
SGI XFS with no debug enabled
c1595b2c c0269328 c03adb9f 00000001 dfe55800 c03adb7c 00000156 c024f1b9
00000000 dfc32000 dfc34e8c c024f1b9 dfc34e8c dfc32000 00000000 dfe56140 00000000 c1595b9c 00000002 dfe56200 c1595b8c c1595b98 00000006 dfe55800 Call Trace: [<c0269328>] [<c024f1b9>] [<c024f1b9>] [<c024c584>] [<c024d894>] [<c02badeb>] [<c02a20c8>] [<c0298926>] [<c0298a12>] [<c0285d67>] [<c029a170>] [<c028647e>] [<c029077c>] [<c029ba4b>] [<c02b8708>] [<c02b53ad>] [<c028c4df>] [<c02a3c36>] [<c02b6323>] [<c02b5eae>] [<c020a7c7>] [<c02084fa>] [<c0209166>] [<c021f1ad>] [<c020959d>] [<c02205f3>] [<c0220934>] [<c0220735>] [<c0220d56>]
  [<c01b9655>] [<c01b930c>] [<c01bb78e>] [<c01b92e0>]
Warning (Oops_read): Code line not seen, dumping what data is available


Trace; c0269328 <xfs_btree_check_sblock+68/f0>
Trace; c024f1b9 <xfs_alloc_lookup+129/3a0>
Trace; c024f1b9 <xfs_alloc_lookup+129/3a0>
Trace; c024c584 <xfs_free_ag_extent+234/770>
Trace; c024d894 <xfs_free_extent+c4/f0>
Trace; c02badeb <kmem_zone_zalloc+fb/130>
Trace; c02a20c8 <xfs_trans_get_efd+38/50>
Trace; c0298926 <xlog_recover_process_efi+196/210>
Trace; c0298a12 <xlog_recover_process_efis+72/d0>
Trace; c0285d67 <xfs_iget+137/190>
Trace; c029a170 <xlog_recover_finish+20/d0>
Trace; c028647e <xfs_iunlock+3e/80>
Trace; c029077c <xfs_log_mount_finish+2c/30>
Trace; c029ba4b <xfs_mountfs+76b/eb0>
Trace; c02b8708 <pagebuf_iostart+78/c0>
Trace; c02b53ad <xfs_setsize_buftarg+3d/80>
Trace; c028c4df <xfs_ioinit+1f/40>
Trace; c02a3c36 <xfs_mount+286/420>
Trace; c02b6323 <vfs_mount+43/50>
Trace; c02b5eae <linvfs_read_super+8e/1d0>
Trace; c020a7c7 <check_disk_change+57/140>
Trace; c02084fa <alloc_super+3a/1c0>
Trace; c0209166 <get_sb_bdev+1d6/300>
Trace; c021f1ad <alloc_vfsmnt+9d/e0>
Trace; c020959d <do_kern_mount+15d/170>
Trace; c02205f3 <do_add_mount+a3/180>
Trace; c0220934 <do_mount+1a4/210>
Trace; c0220735 <copy_mount_options+65/c0>
Trace; c0220d56 <sys_mount+b6/150>
Trace; c01b9655 <prepare_namespace+f5/190>
Trace; c01b930c <init+2c/180>
Trace; c01bb78e <arch_kernel_thread+2e/40>
Trace; c01b92e0 <init+0/180>

3c59x: Donald Becker and others. www.scyld.com/network/vortex.html

1 warning issued.  Results may not be reliable.


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
"We all enter this world in the    | Support Electronic Freedom
same way: naked; screaming; soaked |        http://www.eff.org/
in blood. But if you live your     |  http://www.anti-dmca.org/
life right, that kind of thing     |---------------------------
doesn't have to stop there." -- Dana Gould


<Prev in Thread] Current Thread [Next in Thread>