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
>> In one case I've hit XFS_WANT_CORRUPTED_GOTO in
>> xfs_free_ag_extent(). In this particular case the call chain was
>> 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. :)