Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Nagilum <nagilum@nagilum.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help RAID5 reshape Oops / backup-file
Date: Mon, 15 Oct 2007 09:31:23 +1000	[thread overview]
Message-ID: <18194.42699.193194.986448@notabene.brown> (raw)
In-Reply-To: message from Nagilum on Sunday October 14

On Sunday October 14, nagilum@nagilum.org wrote:
> Can someone tell me if I'm on the right track?
> I've now noticed the following:
> # ~/mdadm-2.6.3/mdadm -v -A /dev/md0 /dev/sd[d-e]
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sdd is identified as a member of /dev/md0, slot -1.
> mdadm: /dev/sde is identified as a member of /dev/md0, slot -1.
> mdadm: No suitable drives found for /dev/md0

Hmm... that might be useful..

I just found your earlier email where you said:

> After the machine came back up (on a rescue disk) I thought I'd
> simply have to go through the process again. So I use add add the
> new disk again. 
> Although that worked, I am now unable to resume the growing
> process. 

Using "add add" again was not correct, and should not have been
possible.
You should have simply assembled the array with the full new set of
devices.  Then reshape would have automatically restarted properly.

Can you remember *exactly* what you did?  If I can reproduce the
situation, I can find the best way to fix it and send you something to
try.

NeilBrown

  reply	other threads:[~2007-10-14 23:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 12:25 Help RAID5 reshape Oops / backup-file Nagilum
2007-10-11 23:51 ` Neil Brown
2007-10-12  6:43   ` Nagilum
2007-10-14 16:55     ` Nagilum
2007-10-14 23:31       ` Neil Brown [this message]
2007-10-15 11:55         ` Nagilum
2007-10-15 12:08           ` Nagilum
2007-10-16  1:16           ` Neil Brown
2007-10-16 12:50             ` Nagilum
2007-10-17 13:13               ` Nagilum
  -- strict thread matches above, loose matches on Subject: below --
2007-10-09 18:58 Nagilum

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=18194.42699.193194.986448@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=nagilum@nagilum.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