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. How do I look at trace events ?. Kamal _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
