From: Dave Chinner <david@fromorbit.com>
To: linux-kernel@vger.kernel.org,
"Markus Trippelsdorf" <markus@trippelsdorf.de>,
"Bruno Prémont" <bonbons@linux-vserver.org>,
xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
"Christoph Hellwig" <hch@infradead.org>,
"Alex Elder" <aelder@sgi.com>,
"Dave Chinner" <dchinner@redhat.com>
Subject: Re: 2.6.39-rc3, 2.6.39-rc4: XFS lockup - regression since 2.6.38
Date: Wed, 4 May 2011 23:25:52 +1000 [thread overview]
Message-ID: <20110504132552.GG9114@dastard> (raw)
In-Reply-To: <20110504005736.GA2958@cucamonga.audible.transient.net>
On Wed, May 04, 2011 at 12:57:36AM +0000, Jamie Heilman wrote:
> Dave Chinner wrote:
> > OK, so the common elements here appears to be root filesystems
> > with small log sizes, which means they are tail pushing all the
> > time metadata operations are in progress. Definitely seems like a
> > race in the AIL workqueue trigger mechanism. I'll see if I can
> > reproduce this and cook up a patch to fix it.
>
> Is there value in continuing to post sysrq-w, sysrq-l, xfs_info, and
> other assorted feedback wrt this issue? I've had it happen twice now
> myself in the past week or so, though I have no reliable reproduction
> technique. Just wondering if more data points will help isolate the
> cause, and if so, how to be prepared to get them.
Not really. I think I know where the problem lies, but I currently
lack a reproducer. There's also been another regression I've only
just got to the bottom of, so I haven't really had a chance to focus
properly on this one yet. Log space hangs like this have
historically been difficult to reproduce reliably....
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:[~2011-05-04 13:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 20:44 2.6.39-rc3, 2.6.39-rc4: XFS lockup - regression since 2.6.38 Bruno Prémont
2011-04-27 5:08 ` Dave Chinner
2011-04-27 16:26 ` Bruno Prémont
2011-04-28 19:45 ` Markus Trippelsdorf
2011-04-29 1:19 ` Dave Chinner
2011-04-29 15:18 ` Markus Trippelsdorf
2011-04-29 19:35 ` Bruno Prémont
2011-04-30 14:18 ` Bruno Prémont
2011-05-02 6:15 ` Markus Trippelsdorf
2011-05-02 12:40 ` Dave Chinner
2011-05-04 0:57 ` Jamie Heilman
2011-05-04 13:25 ` Dave Chinner [this message]
2011-05-05 0:21 ` Dave Chinner
2011-05-05 2:26 ` Dave Chinner
2011-05-05 12:21 ` Dave Chinner
2011-05-05 12:39 ` Christoph Hellwig
2011-05-06 1:49 ` Dave Chinner
2011-05-05 20:35 ` Bruno Prémont
2011-05-09 5:57 ` Bruno Prémont
2011-05-08 5:11 ` Jamie Heilman
2011-05-20 11:20 ` Andrey Rahmatullin
2011-05-21 0:14 ` Dave Chinner
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=20110504132552.GG9114@dastard \
--to=david@fromorbit.com \
--cc=aelder@sgi.com \
--cc=bonbons@linux-vserver.org \
--cc=dchinner@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=xfs-masters@oss.sgi.com \
--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