All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: shane-kernel@csy.ca
Cc: linux-raid@vger.kernel.org
Subject: Re: Help with raid1 to raid5 reshape after crash
Date: Wed, 29 Oct 2014 09:24:48 +1100	[thread overview]
Message-ID: <20141029092448.368fbfeb@notabene.brown> (raw)
In-Reply-To: <001001cfefe3$a82538a0$f86fa9e0$@csy.ca>

[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]

On Fri, 24 Oct 2014 16:38:40 -0700 <shane-kernel@csy.ca> wrote:

> Hello all,
> 
> I was converting from a 2 disk raid1 array to a 4 disk raid5 (3+1s) in preparation to convert to a four disk raid6. I added the two additional component devices and did a:
> Mdadm --grow /dev/md1 --level 5 --raid-devices 3

I guess you mean "to a 3 disk raid5 (2+1s)" ...


> And off it went. I had a power failure a good ways in and now when the system boots, it runs the array, attempts to restart the reshape then disk IO locks up hard.
> 
> I figure it is disk IO rather than a complete system lockup as I have about 10 seconds of interactive shell before it locks. If I enter a dmesg command then that command will succeed. After the lockup, subsequent dmesg commands succeed (dmesg is in cache) but another command such as ls will lock up. Cat /proc/mdstat shows the reshape in progress but it doesn't actually progress beyond the point at which the system locks.
> 
> Booting from a USB stick, I tried:
> Mdadm --assemble --readonly
> But that too hangs the system.
> 
> Do I have any recourse beyond just recreating the array and restoring from backup? Kernel is 3.16.

Probably it can be fixed...

Can you include the output of "mdadm -D" instead of just mentioning the
command :-)
Also "mdadm --examine" of each device.
And "mdadm --version".

And
   cat /proc/PID/stack
for and PID which is in "D" state in 'ps'.

NeilBrown

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2014-10-28 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 23:38 Help with raid1 to raid5 reshape after crash shane-kernel
2014-10-28 22:24 ` 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=20141029092448.368fbfeb@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=shane-kernel@csy.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.