From: Dave Chinner <david@fromorbit.com>
To: "Ngo, Andrew" <andrew.ngo@lmco.com>
Cc: v9fs-developer@lists.sourceforge.net, "Johnson,
Je" <je.johnson@lmco.com>,
xfs@oss.sgi.com
Subject: Re: Stale XFS mount for Kernel 2.6.25.14
Date: Thu, 15 Jan 2009 19:50:40 +1100 [thread overview]
Message-ID: <20090115085040.GE8071@disturbed> (raw)
In-Reply-To: <8604545CB7815D419F5FF108D3E434BA037C7555@emss04m05.us.lmco.com>
On Wed, Jan 14, 2009 at 06:50:24PM -0500, Ngo, Andrew wrote:
> Dave,
>
> From time to time I am still experiencing the stale mount. From this
> last email, you want me to issue the 'echo t > /proc/sysrq-trigger'
> command to show all the processes in the machine. Here is the capture
> of the /var/log/messages when I run the command. Please let me know what
> you find out. Thanks...
> Jan 14 18:19:00 4003a6 kernel: date R running task 0 16073 24960
> Jan 14 18:19:00 4003a6 kernel: ffff8101eb0f3d28 ffff8101eb0f3d6c 0000000000000000 ffff8101eb0f3d70
> Jan 14 18:19:00 4003a6 kernel: 0000000000000001 ffffffff802f7ba5 000000018020c228 0000000000001000
> Jan 14 18:19:00 4003a6 kernel: 0000000000000292 ffff8101eb0f3dc8 0000000000000005 ffff8101eb0f3de8
> Jan 14 18:19:00 4003a6 kernel: Call Trace:
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff802f7ba5>] xfs_bmap_search_extents+0x5b/0xe6
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff802fdfa9>] xfs_bmapi+0x26e/0xf89
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff803702f3>] __up_read+0x19/0x7f
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff80314887>] xfs_iunlock+0x57/0x79
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff8032ce6c>] xfs_free_eofblocks+0xb2/0x213
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff8029bc3a>] dput+0x26/0xd5
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff8028a033>] filp_close+0x5d/0x65
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff804c5581>] _write_lock_irq+0xf/0x10
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff80235e93>] do_exit+0x307/0x67a
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff80236275>] do_group_exit+0x6f/0x8a
> Jan 14 18:19:00 4003a6 kernel: [<ffffffff8020bc9b>] system_call_after_swapgs+0x7b/0x80
That's the only stack trace that has any XFS references in it.
Do you have a 'date' process stuck on your machine or was this just
a "lucky" occurrence?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-15 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8604545CB7815D419F5FF108D3E434BA017C6427@emss04m05.us.lmco.com>
[not found] ` <20081020230802.GA18495@disturbed>
2008-11-03 20:49 ` Stale XFS mount for Kernel 2.6.25.14 Ngo, Andrew
2008-11-04 6:05 ` Dave Chinner
2009-01-14 23:50 ` Ngo, Andrew
2009-01-15 8:50 ` Dave Chinner [this message]
2008-10-13 2:10 Ngo, Andrew
2008-10-13 3:59 ` Dave Chinner
2008-10-13 12:06 ` Ngo, Andrew
2008-10-14 2:04 ` Ngo, Andrew
2008-10-14 2:15 ` Dave Chinner
2008-10-14 3:40 ` Ngo, Andrew
2008-10-14 5:53 ` Dave Chinner
2008-10-14 21:54 ` Ngo, Andrew
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=20090115085040.GE8071@disturbed \
--to=david@fromorbit.com \
--cc=andrew.ngo@lmco.com \
--cc=je.johnson@lmco.com \
--cc=v9fs-developer@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.