http://oss.sgi.com/bugzilla/show_bug.cgi?id=765
Summary: xfs_force_shutdown(dm-0,0x8) called from line 1091 of
file fs/xfs/xfs_trans.c
Product: Linux XFS
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: blocker
Priority: P1
Component: XFS kernel code
AssignedTo: xfs-master@xxxxxxxxxxx
ReportedBy: pnealy@xxxxxxxxxxx
Kernel: 2.6.12.6 with some tweaks but none to xfs.
We are getting the following on a very repeated basis on our NAS appliances:
Jun 1 10:18:46 localhost kernel: xfs_force_shutdown(dm-0,0x8) called from line
1091 of file fs/xfs/xfs_trans.c. Return address = 0xf9003a1b
Jun 1 10:18:46 localhost kernel: Filesystem "dm-0": Corruption of in-memory
data detected. Shutting down filesystem: dm-0
Jun 1 10:18:46 localhost kernel: Please umount the filesystem, and rectify the
problem(s)
Jun 21 10:39:06 localhost kernel: xfs_force_shutdown(dm-0,0x8) called from line
1091 of file fs/xfs/xfs_trans.c. Return address = 0xf9003a1b
Jun 21 10:39:06 localhost kernel: Filesystem "dm-0": Corruption of in-memory
data detected. Shutting down filesystem: dm-0
Jun 21 10:39:06 localhost kernel: Please umount the filesystem, and rectify the
problem(s)
Our implementation runs LVM on top of XFS. We're unsure what is going on, but
doing an xfs repair does not remedy the situation. We cannot make them fail at
will, but the failure rate can be as short as two weeks, which is unacceptable.
We've had more than one customer site fail in the exact same way. Many of these
customers use our NAS appliance with tools such as Adobe Premier for doing video
editing.
What can we do up front to provide you with more information about the failure.
These are systems out in the field (we are unable to recreate them here), so
are there any switches we can throw to the fs layer to maybe turn on more debug?
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|