From: Ed Cashin <ecashin@coraid.com>
To: linux-xfs@oss.sgi.com
Cc: ecashin@coraid.com
Subject: Re: NULL mp->m_log in 2.6.31 xfs_log_move_tail
Date: Mon, 09 Nov 2009 16:41:58 -0500 [thread overview]
Message-ID: <87fx8n8jfd.fsf@coraid.com> (raw)
In-Reply-To: 20091109211620.GA22777@infradead.org
Christoph Hellwig <hch@infradead.org> writes:
> 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.
>>
>> I looked at the trace (included below) and put in the following check:
>
> Given that you seem to be able to reproduce it can you see if the patch
> below helps:
>
> Index: linux-2.6/fs/xfs/xfs_log.c
> ===================================================================
> --- linux-2.6.orig/fs/xfs/xfs_log.c 2009-11-09 22:09:08.858026060 +0100
> +++ linux-2.6/fs/xfs/xfs_log.c 2009-11-09 22:13:13.958255857 +0100
> @@ -1602,6 +1602,8 @@ xlog_dealloc_log(xlog_t *log)
> xlog_in_core_t *iclog, *next_iclog;
> int i;
>
> + xfs_flush_buftarg(log->l_mp->m_logdev_targp, 1);
> +
> iclog = log->l_iclog;
> for (i=0; i<log->l_iclog_bufs; i++) {
> sv_destroy(&iclog->ic_force_wait);
>
Thanks. I am not sure when we'll be able to try it, because the one
who discovered this issue is not currently available, but I'll try to
fit it in one way or another. A lot of folks using AoE use XFS.
--
Ed Cashin <ecashin@coraid.com>
http://www.coraid.com/
http://noserose.net/e/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-11-09 21:42 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
2009-11-09 21:16 ` Christoph Hellwig
2009-11-09 21:41 ` Ed Cashin [this message]
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=87fx8n8jfd.fsf@coraid.com \
--to=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