raid0 to raid10 takeover bug

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?

Regards- Krzysztof
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: raid0 to raid10 takeover bug

On Thu, 16 Dec 2010 14:50:42 +0000 "Wojcik, Krzysztof"
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

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html