From: NeilBrown <neilb@suse.de>
To: Bryan Bush <bbushvt@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 grow failed
Date: Mon, 2 Apr 2012 09:54:25 +1000 [thread overview]
Message-ID: <20120402095425.168e5d94@notabene.brown> (raw)
In-Reply-To: <CAJ72viPw=QrETGPU5OwBgL-GXfCUfqfbWCSAvp2_yzzxuJeT1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
On Sun, 1 Apr 2012 03:05:29 -0400 Bryan Bush <bbushvt@gmail.com> wrote:
> Additional info that might be useful. When I specify which disks to
> use in the array, I get this
> root@diamond:/# mdadm -A --verbose /dev/md1 /dev/sd[onjlkuhedcb]1
> mdadm: looking for devices for /dev/md1
> mdadm: /dev/sdb1 is identified as a member of /dev/md1, slot 4.
> mdadm: /dev/sdc1 is identified as a member of /dev/md1, slot 5.
> mdadm: /dev/sdd1 is identified as a member of /dev/md1, slot 6.
> mdadm: /dev/sde1 is identified as a member of /dev/md1, slot 7.
> mdadm: /dev/sdh1 is identified as a member of /dev/md1, slot 12.
> mdadm: /dev/sdj1 is identified as a member of /dev/md1, slot 10.
> mdadm: /dev/sdk1 is identified as a member of /dev/md1, slot 8.
> mdadm: /dev/sdl1 is identified as a member of /dev/md1, slot 0.
> mdadm: /dev/sdn1 is identified as a member of /dev/md1, slot 2.
> mdadm: /dev/sdo1 is identified as a member of /dev/md1, slot 3.
> mdadm: device 8 in /dev/md1 has wrong state in superblock, but
> /dev/sdk1 seems ok
> mdadm: device 10 in /dev/md1 has wrong state in superblock, but
> /dev/sdj1 seems ok
> mdadm: device 12 in /dev/md1 has wrong state in superblock, but
> /dev/sdh1 seems ok
> mdadm: SET_ARRAY_INFO failed for /dev/md1: Device or resource busy
> root@diamond:/#
1/ Are you absolutely certain you did
mdadm -S /dev/md1
first? Because it really looks like you didn't.
2/ Any kernel log messages?
dmesg | tail -n 50
immediately after the failed "mdadm -A" command.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-04-01 23:54 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
2012-03-31 23:24 ` Bryan Bush
2012-04-01 7:05 ` Bryan Bush
2012-04-01 23:54 ` NeilBrown [this message]
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=20120402095425.168e5d94@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