From: Dave Chinner <david@fromorbit.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: "Dave Chinner" <dchinner@redhat.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
"Christoph Hellwig" <hch@infradead.org>,
xfs-masters@oss.sgi.com,
"Bruno Prémont" <bonbons@linux-vserver.org>,
"Alex Elder" <aelder@sgi.com>
Subject: Re: 2.6.39-rc3, 2.6.39-rc4: XFS lockup - regression since 2.6.38
Date: Fri, 29 Apr 2011 11:19:29 +1000 [thread overview]
Message-ID: <20110429011929.GA13542@dastard> (raw)
In-Reply-To: <20110428194528.GA1627@x4.trippels.de>
On Thu, Apr 28, 2011 at 09:45:28PM +0200, Markus Trippelsdorf wrote:
> On 2011.04.27 at 18:26 +0200, Bruno Prémont wrote:
> > On Wed, 27 April 2011 Dave Chinner <david@fromorbit.com> wrote:
> > > On Sat, Apr 23, 2011 at 10:44:03PM +0200, Bruno Prémont wrote:
> > > > Running 2.6.39-rc3+ and now again on 2.6.39-rc4+ (I've not tested -rc1
> > > > or -rc2) I've hit a "dying machine" where processes writing to disk end
> > > > up in D state.
> > > > From occurrence with -rc3+ I don't have logs as those never hit the disk,
> > > > for -rc4+ I have the following (sysrq+t was too big, what I have of it
> > > > misses a dozen of kernel tasks - if needed, please ask):
> > > >
> > > > The -rc4 kernel is at commit 584f79046780e10cb24367a691f8c28398a00e84
> > > > (+ 1 patch of mine to stop disk on reboot),
> > > > full dmesg available if needed; kernel config attached (only selected
> > > > options). In case there is something I should do at next occurrence
> > > > please tell. Unfortunately I have no trigger for it and it does not
> > > > happen very often.
> > > >
> > > > [ 0.000000] Linux version 2.6.39-rc4-00120-g73b5b55 (kbuild@neptune) (gcc version 4.4.5 (Gentoo 4.4.5 p1.2, pie-0.4.5) ) #12 Thu Apr 21 19:28:45 CEST 2011
> > > >
> > > >
> > > > [32040.120055] INFO: task flush-8:0:1665 blocked for more than 120 seconds.
> > > > [32040.120068] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > > > [32040.120077] flush-8:0 D 00000000 4908 1665 2 0x00000000
> > > > [32040.120099] f55efb5c 00000046 00000000 00000000 00000000 00000001 e0382924 00000000
> > > > [32040.120118] f55efb0c f55efb5c 00000004 f629ba70 572f01a2 00001cfe f629ba70 ffffffc0
> > > > [32040.120135] f55efc68 f55efb30 f889d7f8 f55efb20 00000000 f55efc68 e0382900 f55efc94
> > > > [32040.120153] Call Trace:
> > > > [32040.120220] [<f889d7f8>] ? xfs_bmap_search_multi_extents+0x88/0xe0 [xfs]
> > > > [32040.120239] [<c109ce1d>] ? kmem_cache_alloc+0x2d/0x110
> > > > [32040.120294] [<f88c88ca>] ? xlog_space_left+0x2a/0xc0 [xfs]
> > > > [32040.120346] [<f88c85cb>] xlog_wait+0x4b/0x70 [xfs]
> > > > [32040.120359] [<c102ca00>] ? try_to_wake_up+0xc0/0xc0
> > > > [32040.120411] [<f88c948b>] xlog_grant_log_space+0x8b/0x240 [xfs]
> > > > [32040.120464] [<f88c936e>] ? xlog_grant_push_ail+0xbe/0xf0 [xfs]
> > > > [32040.120516] [<f88c99db>] xfs_log_reserve+0xab/0xb0 [xfs]
> > > > [32040.120571] [<f88d6dc8>] xfs_trans_reserve+0x78/0x1f0 [xfs]
> > >
> > > Hmmmmm. That may be caused by the conversion of the xfsaild to a
> > > work queue. Can you post the output of "xfs_info <mntpt>" and the
> > > mount options (/proc/mounts) used on you system?
>
> I may have hit the same problem today and managed to capture some sysrq-l
> and sysrq-w output.
>
> The system was largely unusable during this incident. I could still
> switch between X and the console (and press the sysrq key-combination),
> but I couldn't run any commands in the terminal.
>
>
> x4 ~ # xfs_info /
> meta-data=/dev/root isize=256 agcount=4, agsize=1949824 blks
> = sectsz=512 attr=2
> data = bsize=4096 blocks=7799296, imaxpct=25
> = sunit=128 swidth=128 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=3808, version=2
> = sectsz=512 sunit=8 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
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.
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-04-29 1:16 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 [this message]
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
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=20110429011929.GA13542@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