http://oss.sgi.com/bugzilla/show_bug.cgi?id=765
------- Additional Comments From sandeen-xfs@xxxxxxxxxxx 2007-08-14 12:25 CST
-------
Looks like it's canceling a dirty transaction:
1084 /*
1085 * See if the caller is relying on us to shut down the
1086 * filesystem. This happens in paths where we detect
1087 * corruption and decide to give up.
1088 */
1089 if ((tp->t_flags & XFS_TRANS_DIRTY) &&
1090 !XFS_FORCED_SHUTDOWN(tp->t_mountp))
1091 xfs_force_shutdown(tp->t_mountp, XFS_CORRUPT_INCORE);
2.6.12 is awfully old, but I understand that it's an embedded product.
There may have been a fix for this since then, it rings a bell, but I don't
recall offhand.
You could set the panic mask sysctl:
fs.xfs.panic_mask (Min: 0 Default: 0 Max: 127)
Causes certain error conditions to call BUG(). Value is a bitmask;
AND together the tags which represent errors which should cause panics:
XFS_NO_PTAG 0
XFS_PTAG_IFLUSH 0x00000001
XFS_PTAG_LOGRES 0x00000002
XFS_PTAG_AILDELETE 0x00000004
XFS_PTAG_ERROR_REPORT 0x00000008
XFS_PTAG_SHUTDOWN_CORRUPT 0x00000010
XFS_PTAG_SHUTDOWN_IOERROR 0x00000020
XFS_PTAG_SHUTDOWN_LOGERROR 0x00000040
to trip a panic when you get a shutdown; you could then get a BUG, backtrace,
and perhaps a dump at the moment shutdown was called... though I don't know if
that's feasible in the field.
-Eric
--
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.
|