On 5/15/13 5:10 PM, Ben Myers wrote: > Hey Chris, > > On Wed, May 15, 2013 at 03:58:35PM -0600, Chris Friesen wrote: >> As I mentioned before I'm digging into some intermittent xfs >> corruption issues on an embedded system running a 2.6.27-based >> kernel. >> >> In one case I've hit XFS_WANT_CORRUPTED_GOTO in >> xfs_free_ag_extent(). In this particular case the call chain was >> >> xfs_free_ag_extent+0x55d/0x6e0 >> xfs_free_extent+0xac/0xd0 >> xfs_bmap_finish+0x156/0x1a0 >> xfs_itruncate_finish+0x137/0x340 >> xfs_inactive+0x386/0x4b0 >> xfs_fs_clear_inode+0xc6/0x120 >> clear_inode+0x58/0x110 >> generic_delete_inode+0xff/0x110 >> generic_drop_inode+0x16d/0x190 >> iput+0x5d/0x70 >> do_unlinkat+0x147/0x280 >> sys_unlinkat+0x1d/0x40 >> >> I have two questions: >> >> 1) do_unlinkat() has the filesystem path, but iput() returns void. >> Is there any way for me to add instrumentation to xfs_inactive() to >> work backwards from the xfs_inode_t pointer to print out a path to >> the file being deleted? > > Use VFS_I to get to a 'struct inode' and from there you can look at the > dentries on i_dentry list and traverse back through the path by looking at > d_parent. Might be easier to just print the path in do_unlinkat? or just print out the inode nr (i_ino) and do a find -inum after the fact. :) -Eric </lazy> _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
