From: Neil Brown <neilb@suse.de>
To: "Wojcik, Krzysztof" <krzysztof.wojcik@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: raid0 to raid10 takeover bug
Date: Fri, 17 Dec 2010 10:24:57 +1100 [thread overview]
Message-ID: <20101217102457.3ec8c8da@notabene.brown> (raw)
In-Reply-To: <BE2BFE91933D1B4089447C644860408066B83882@irsmsx503.ger.corp.intel.com>
On Thu, 16 Dec 2010 14:50:42 +0000 "Wojcik, Krzysztof"
<krzysztof.wojcik@intel.com> wrote:
> Hi,
>
> I would like to report a bug connected with raid0 to raid10 takeover operation.
> When we add a spare drive to array after takeover, recovery process has been triggered but it is not finish- it stops at about 90%.
> "resync" process is in uninterruptable sleep state (D). Deadlock?
> It is reproducible on native and imsm metadata.
> Any ideas, suggestions?
>
I would start by getting a stack trace of all relevant processes, with by
echo t > /proc/sysrq-trigger
or
cat /proc/XXXX/stack
Find out where the processes is waiting.
An 'D' stands for 'Disk wait' rather than 'Deadlock'.
It is a by if an anachronistic name as it is really any uninterruptible wait,
which can be for things other than waiting for Disk.
NeilBrown
prev parent reply other threads:[~2010-12-16 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 14:50 raid0 to raid10 takeover bug Wojcik, Krzysztof
2010-12-16 23:24 ` Neil Brown [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=20101217102457.3ec8c8da@notabene.brown \
--to=neilb@suse.de \
--cc=krzysztof.wojcik@intel.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).