On Fri, Nov 02, 2012 at 09:57:27PM -0400, Kamal Dasu wrote: > Dave, > > > > > > 0x780dbd80007f248 > > > > Once again it's corruption in the upper 32 bits of the 64 bit number. > > Those bits should be zero. Perhaps looking at all the trace events > > from recovery might give you a closer approximation of where the bad > > extent records is found.... > > I have been trying to use the xfs_db xfs_logprint, how ever > xfs_logprint bails out when it finds an error. $ man xfs_logprint .... -c Attempt to continue when an error is detected. > How do I look at > trace events ?. Documentation/trace/events.txt Or better yet, use trace-cmd as suggested in the FAQ: http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
