Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Bryan Bush <bbushvt@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 grow failed
Date: Sun, 1 Apr 2012 08:00:36 +1000	[thread overview]
Message-ID: <20120401080036.355a8a23@notabene.brown> (raw)
In-Reply-To: <CAJ72viPH9AykY-tafTChcS0ZbP0gGaiKRybafs4C4Yk-8D=g3A@mail.gmail.com>

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

On Sat, 31 Mar 2012 15:38:23 -0400 Bryan Bush <bbushvt@gmail.com> wrote:

> I've had another md issue.  Not sure exactly what caused it but my
> array is offline again.  The reshape completed and I was about to
> insert a new drive to replace the one that failed on the initial
> reshape.
> /proc/mdstat contains
> md1 : inactive sdk1[13](S) sdh1[9](S) sdi1[10](S) sdc1[8](S)
> sdj1[11](S) sdb1[4](S) sdd1[6](S) sde1[7](S) sdl1[0](S) sdn1[2](S)
> sdo1[3](S)
>       21488647746 blocks super 1.2
> 
> "mdadm -As --verbose /dev/md1 -u fa32e2c5:e7bda20b:32af7c90:c7ee61eb" returns
> mdadm: looking for devices for /dev/md1
> <cut>
> mdadm: /dev/sdo1 is identified as a member of /dev/md1, slot 3.
> mdadm: /dev/sdn1 is identified as a member of /dev/md1, slot 2.
> mdadm: /dev/sdj1 is identified as a member of /dev/md1, slot 10.
> mdadm: /dev/sdl1 is identified as a member of /dev/md1, slot 0.
> mdadm: /dev/sdk1 is identified as a member of /dev/md1, slot 8.
> mdadm: /dev/sdi1 is identified as a member of /dev/md1, slot 11.
> mdadm: /dev/sdh1 is identified as a member of /dev/md1, slot 12.
> mdadm: /dev/sde1 is identified as a member of /dev/md1, slot 7.
> mdadm: /dev/sdd1 is identified as a member of /dev/md1, slot 6.
> mdadm: /dev/sdc1 is identified as a member of /dev/md1, slot 5.
> mdadm: /dev/sdb1 is identified as a member of /dev/md1, slot 4.
> mdadm: Cannot open /dev/sdl1: Device or resource busy

Stop the array first. - it is half-started which confused mdadm.
i.e
   mdadm -S /dev/md1
   mdadm -As .......

NeilBrown


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

  reply	other threads:[~2012-03-31 22:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  2:44 RAID6 grow failed Bryan Bush
2012-03-28  3:22 ` Mathias Burén
2012-03-28  4:18 ` NeilBrown
2012-03-28  7:54   ` Bryan Bush
2012-03-28  8:26     ` NeilBrown
2012-03-28 10:35       ` Bryan Bush
2012-03-31 19:38         ` Bryan Bush
2012-03-31 22:00           ` NeilBrown [this message]
2012-03-31 23:24             ` Bryan Bush
2012-04-01  7:05               ` Bryan Bush
2012-04-01 23:54                 ` NeilBrown
2012-04-02  0:02                   ` Bryan Bush
2012-04-02  0:26                     ` NeilBrown
2012-04-02  0:44                       ` Bryan Bush
2012-04-02  2:12                         ` NeilBrown
2012-04-02  2:59                           ` Bryan Bush

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=20120401080036.355a8a23@notabene.brown \
    --to=neilb@suse.de \
    --cc=bbushvt@gmail.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