From: NeilBrown <neilb@suse.de>
To: hans@hanswkraus.com
Cc: linux-raid@vger.kernel.org
Subject: Re: More 'D' state processes [was: Re: Weird problem: mdadm blocks]
Date: Tue, 7 Jan 2014 11:23:05 +1100 [thread overview]
Message-ID: <20140107112305.0e8ff837@notabene.brown> (raw)
In-Reply-To: <2b3bc4b9893fa3dee2944c249722d863@hanswkraus.com>
[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]
On Mon, 06 Jan 2014 17:00:35 +0100 hans@hanswkraus.com wrote:
>
>
> Hi Neil,
>
> the output of 'uname -r' is: 3.2.0-4-amd64. A standard Debian Wheezy.
>
> I rebooted the system in the meantime. The re-sync started anew but
> finished otherwise without flaws.
I guess there must be some other bug then. I still expect that it is related
to md_flush_request(). Probably related to the fact that you have an md
device on top of other md devices....
I had a quick look and cannot find the cause of the problem. Maybe it will
have to wait until someone else hit it :-(
Thanks for the report,
NeilBrown
>
> Regards, Hans
>
> Am 05.01.2014 23:00, schrieb NeilBrown:
>
> > On Sun, 22 Dec 2013 17:43:43 +0100 Hans Kraus <hans@hanswkraus.com> wrote:
> >
> >> Hi Neil,
> >
> > Hi Hans,
> > sorry for the delay - Christmas/New Year vacation...
> > [40800.777037] xfsaild/dm-0 D ffff88003754c300 0 20798 2 0x00000000 [40800.777042] ffff88003754c300 0000000000000046 0000000000000000 ffff88005d7c51a0 [40800.777047] 0000000000013780 ffff88001b01ffd8 ffff88001b01ffd8 ffff88003754c300 [40800.777052] ffff880071fede00 ffffffff81070fc1 0000000000000046 ffff88003734a400 [40800.777057] Call Trace: [40800.777061] [<ffffffff81070fc1>] ? arch_local_irq_save+0x11/0x17 [40800.777071] [<ffffffffa0170466>] ? md_flush_request+0x96/0x111 [md_mod] [40800.777076] [<ffffffff8103f6c4>] ? try_to_wake_up+0x197/0x197 [40800.777082] [<ffffffffa0f11711>] ? make_request+0x25/0x37a [raid456] [40800.777091] [<ffffffffa0185873>] ?
>
> This looks like the most likely root of the problem - something wrong in
> md_flush_request.
>
> There was a bug here fixed in 2.6.37
>
> commit a035fc3e2531703b539f23bec4ca7943cfc69349
> Author: NeilBrown <neilb@suse.de>
> Date: Thu Dec 9 16:17:51 2010 +1100
>
> md: fix possible deadlock in handling flush requests.
>
> You didn't say which kernel you were running. Could it be earlier than
> 2.6.37???
>
> NeilBrown
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2014-01-07 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 9:01 Weird problem: mdadm blocks Hans Kraus
2013-12-22 11:19 ` NeilBrown
2013-12-22 16:11 ` Hans Kraus
2013-12-22 16:43 ` More 'D' state processes [was: Re: Weird problem: mdadm blocks] Hans Kraus
2014-01-05 22:00 ` NeilBrown
[not found] ` <2b3bc4b9893fa3dee2944c249722d863@hanswkraus.com>
2014-01-07 0:23 ` 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=20140107112305.0e8ff837@notabene.brown \
--to=neilb@suse.de \
--cc=hans@hanswkraus.com \
--cc=linux-raid@vger.kernel.org \
/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).