Thanks for the reply.
> Are you hitting http://oss.sgi.com/projects/xfs/faq.html#dir2 ?
Presumably not - i'm using 2.6.17.11, and that information indicates the
bug was fixed in 2.6.17.7.
I've attached the output from running ksymoops on messages.1. First
crash/trace (Feb 21 19:xx) corresponds to the original XFS event; the
second (Feb 22 15:xx) is the system going down when i tried to unmount the
volume.
Here are the additional syslog msgs corresponding to the Feb 22 15:xx
crash.
Feb 22 15:47:13 qln01 kernel: grsec: From 10.0.2.93: unmount of /dev/sda1
by /bin/umount[umount:18604] uid/euid:0/0 gid/egid:0/0, parent
/bin/bash[bash:31972] uid/euid:0/0 gid/egid:0/0
Feb 22 15:47:14 qln01 kernel: xfs_force_shutdown(sda1,0x1) called from
line 338 of file fs/xfs/xfs_rw.c. Return address = 0xffffffff88173ce4
Feb 22 15:47:14 qln01 kernel: xfs_force_shutdown(sda1,0x1) called from
line 338 of file fs/xfs/xfs_rw.c. Return address = 0xffffffff88173ce4
Feb 22 15:47:28 qln01 kernel: BUG: soft lockup detected on CPU#0!
thanks
slaton
ksymoops.txt
Description: Text document
|