linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Dave Chinner <david@fromorbit.com>,
	xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
	Christoph Hellwig <hch@infradead.org>,
	Alex Elder <aelder@sgi.com>, Dave Chinner <dchinner@redhat.com>,
	linux-kernel@vger.kernel.org,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: 2.6.39-rc3, 2.6.39-rc4: XFS lockup - regression since 2.6.38
Date: Sat, 30 Apr 2011 16:18:10 +0200	[thread overview]
Message-ID: <20110430161810.6ccd2c99@neptune.home> (raw)
In-Reply-To: <20110429213524.449e003b@neptune.home>

On Fri, 29 April 2011 Bruno Prémont wrote:
> On Fri, 29 April 2011 Markus Trippelsdorf wrote:
> > On 2011.04.29 at 11:19 +1000, 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.
> > 
> > Hmm, I'm wondering if this issue is somehow related to the hrtimer bug,
> > that Thomas Gleixner fixed yesterday:
> > http://git.us.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commit;h=ce31332d3c77532d6ea97ddcb475a2b02dd358b4
> > http://thread.gmane.org/gmane.linux.kernel.mm/61909/
> > 
> > It also looks similar to the issue that James Bottomley reported
> > earlier: http://thread.gmane.org/gmane.linux.kernel.mm/62185/ 
> 
> I'm going to see, I've applied Thomas' fix on the box seeing XFS freeze (without
> other changes to kernel).
> Going to run that kernel for the week-end and beyond if it survives to see what
> happens.

Happened again (after a few hours of uptime), so it definitely is not
caused by hrtimer bug that Thomas Gleixner fixed.

Bruno

  reply	other threads:[~2011-04-30 14:18 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 [this message]
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
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=20110430161810.6ccd2c99@neptune.home \
    --to=bonbons@linux-vserver.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=aelder@sgi.com \
    --cc=david@fromorbit.com \
    --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;
as well as URLs for NNTP newsgroup(s).