From: NeilBrown <neilb@suse.de>
To: Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk>
Cc: Torsten Kaiser <just.for.lkml@googlemail.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Hang in md-raid1 with 3.7-rcX
Date: Thu, 29 Nov 2012 07:26:46 +1100 [thread overview]
Message-ID: <20121129072646.0bcb3a2a@notabene.brown> (raw)
In-Reply-To: <32242311.8QXFMOUYz5@deuteros>
[-- Attachment #1: Type: text/plain, Size: 2106 bytes --]
On Wed, 28 Nov 2012 14:51:59 +0000 Tvrtko Ursulin
<tvrtko.ursulin@onelan.co.uk> wrote:
> On Tuesday 27 November 2012 12:05:28 NeilBrown wrote:
> > On Sat, 24 Nov 2012 10:18:44 +0100 Torsten Kaiser
> >
> > <just.for.lkml@googlemail.com> wrote:
> > > After my system got stuck with 3.7.0-rc2 as reported in
> > > http://marc.info/?l=linux-kernel&m=135142236520624 LOCKDEP seem to
> > > blame XFS, because it found 2 possible deadlocks. But after these
> > > locking issues where fixed, my system got stuck again with 3.7.0-rc6
> > > as reported in http://marc.info/?l=linux-kernel&m=135344072325490
> > > Dave Chinner thinks its an issue within md, that it gets stuck and
> > > that will then prevent any further xfs activity, and that I should
> > > report it to the raid mailing list.
> > >
> > > The issue seems to be that multiple processes (kswapd0, xfsaild/md4
> > > and flush-9:4) get stuck in md_super_wait() like this:
> > > [<ffffffff816b1224>] schedule+0x24/0x60
> > > [<ffffffff814f9dad>] md_super_wait+0x4d/0x80
> > > [<ffffffff8105ca30>] ? __init_waitqueue_head+0x60/0x60
> > > [<ffffffff81500753>] bitmap_unplug+0x173/0x180
> > > [<ffffffff810b6acf>] ? write_cache_pages+0x12f/0x420
> > > [<ffffffff810b6700>] ? set_page_dirty_lock+0x60/0x60
> > > [<ffffffff814e8eb8>] raid1_unplug+0x98/0x110
> > > [<ffffffff81278a6d>] blk_flush_plug_list+0xad/0x240
> > > [<ffffffff81278c13>] blk_finish_plug+0x13/0x50
> > >
> > > The full hung-tasks stack traces and the output from SysRq+W can be
> > > found at http://marc.info/?l=linux-kernel&m=135344072325490 or in the
> > > LKML thread 'Hang in XFS reclaim on 3.7.0-rc3'.
> >
> > Yes, it does look like an md bug....
> > Can you test to see if this fixes it?
>
> Hi,
>
> Would this bug be present in 3.6 as well? Because I am hitting something which
> looks pretty much like this with 3.6.x. In which case it should go to -stable,
> however I am not able to test on the affected machine at the moment.
>
> Regards,
>
> Tvrtko
Yes it is in 3.6, and it will go to -stable.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-11-28 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 9:18 Hang in md-raid1 with 3.7-rcX Torsten Kaiser
2012-11-27 1:05 ` NeilBrown
2012-11-27 7:08 ` Torsten Kaiser
2012-12-02 12:10 ` Torsten Kaiser
2012-12-02 19:52 ` NeilBrown
[not found] ` <32242311.8QXFMOUYz5@deuteros>
2012-11-28 20:26 ` NeilBrown [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=20121129072646.0bcb3a2a@notabene.brown \
--to=neilb@suse.de \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=tvrtko.ursulin@onelan.co.uk \
/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).