From: Ben Myers <bpm@sgi.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: Alex Elder <elder@kernel.org>, xfs@oss.sgi.com
Subject: Re: given a pointer to xfs_inode_t, how to determine path?
Date: Mon, 17 Sep 2012 11:21:20 -0500 [thread overview]
Message-ID: <20120917162120.GG25175@sgi.com> (raw)
In-Reply-To: <50574709.9000301@genband.com>
Hi Chris,
On Mon, Sep 17, 2012 at 09:51:37AM -0600, Chris Friesen wrote:
> We're running 2.6.27 (upgrading not currently possible, embedded product).
>
> We had a situation arise where we could see in stack traces that a
> number of tasks were stuck in vn_iowait(). That function takes a
> pointer to xfs_inode_t. Given that, would it be possible to work
> backwards to determine a filesystem path corresponding to that
> inode? I realize it would likely only go back to the head of the
> filesystem, but that would be fine.
Yep, it's possible.
echo t > /proc/sysrq-trigger won't give you the full stack, but you may be able
to get an idea of what is going on, well enough to make some guesses as to the
culprit. That's probably your best first step.
If you have crash installed:
1) disassemble vn_iowait and find out which register the xfs_inode_t pointer is in.
2) print out the full stacks of all the processes in the system. 'bt -f', I think.
3) grep for the xfs_inode_t pointer on those stacks.
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-09-17 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 15:51 given a pointer to xfs_inode_t, how to determine path? Chris Friesen
2012-09-17 16:21 ` Ben Myers [this message]
2012-09-17 22:49 ` Dave Chinner
2012-09-19 15:15 ` Ben Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120917162120.GG25175@sgi.com \
--to=bpm@sgi.com \
--cc=chris.friesen@genband.com \
--cc=elder@kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox