From: Christoph Hellwig <hch@infradead.org>
To: Ed Cashin <ecashin@coraid.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: NULL mp->m_log in 2.6.31 xfs_log_move_tail
Date: Mon, 9 Nov 2009 16:05:19 -0500 [thread overview]
Message-ID: <20091109210519.GA9698@infradead.org> (raw)
In-Reply-To: <87ws1z8mbf.fsf@coraid.com>
On Mon, Nov 09, 2009 at 03:39:32PM -0500, Ed Cashin wrote:
> A colleague has seen oopses in 2.6.31 when an XFS is mounted on an AoE
> target that becomes unresponsive and is marked as "down" by the aoe
> driver. The aoe driver starts failing all new I/O requests after
> failing all current requests when the device is down.
And the oops happens when unmounting the devices? That's at least how
the trace looks like. If that's the case I suspect we tear down the
log a bit too early - I'll do an audit of the log shutdown path how this
could happen.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-11-09 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 20:39 NULL mp->m_log in 2.6.31 xfs_log_move_tail Ed Cashin
2009-11-09 21:05 ` Christoph Hellwig [this message]
2009-11-09 21:16 ` Christoph Hellwig
2009-11-09 21:41 ` Ed Cashin
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=20091109210519.GA9698@infradead.org \
--to=hch@infradead.org \
--cc=ecashin@coraid.com \
--cc=linux-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