http://oss.sgi.com/bugzilla/show_bug.cgi?id=272
Summary: xfs_force_shutdown in xfs_trans_cancel, part 2
Product: Linux XFS
Version: Current
Platform: IA32
OS/Version: Linux
Status: NEW
Severity: normal
Priority: High
Component: XFS kernel code
AssignedTo: xfs-master@xxxxxxxxxxx
ReportedBy: mi-xfs@xxxxxxxxxxx
I am seeing a problem very similar to the one described in bug
#186. I wasn't sure if it's the same problem so I am creating a new
ticket:
xfs_force_shutdown(sd(8,5),0x8) called from line 1071 of file xfs_trans.c.
Return address = 0xc024d1fb
Filesystem "sd(8,5)": Corruption of in-memory data detected. Shutting down
filesystem: sd(8,5)
Please umount the filesystem, and rectify the problem(s)
That line is in xfs_trans_cancel().
unmounting and remounting results in a clean filesystem, xfs_repair
doesn't find any errors.
I started seeing this about 10 days ago, running linux-2.4.20 plus the
latest xfs-2.4.20-all-i386.bz2 that was available on Jan 20
2003. Previous to that this system has been running without problems
for several months, with the same kernel. Since then the same error
has been occurring once in about every 48 hours. I have tried
2.4.21+xfs-1.3.0pre4 and 1.3.0pre5 and the latest xfs-2.4.21-all as
well, all versions produce the error.
All of these kernels have the fix proposed in bug #186.
I am fairly confident that there are no hardware problems, I just ran
my burn-in script on the machine for 24 hours without any errors.
About the system:
Fairly heavily loaded NFS server, SMP (2xPIII), 1G RAM, Intel e1000,
Adaptec 3210S hardware raid (showing all disks optimal).
Please let me know if you would like any other info or if you want me
to do any tests. I have just rebooted the system with a kdb enabled
kernel.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|