From: NeilBrown <neilb@suse.de>
To: "RANSOM, Tony" <tony.ransom@baesystems.com>
Cc: "'linux-raid@vger.kernel.org'" <linux-raid@vger.kernel.org>
Subject: Re: Problem rebuild raid 1 replacement disk
Date: Mon, 20 Feb 2012 21:51:47 +1100 [thread overview]
Message-ID: <20120220215147.7684efda@notabene.brown> (raw)
In-Reply-To: <807765805CA0DF48898D4C016E982BFC065A6D9BF6@MWLSVEXM002.au.baesystems.com>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
On Mon, 20 Feb 2012 19:45:24 +1030 "RANSOM, Tony"
<tony.ransom@baesystems.com> wrote:
> Neil,
>
> >Yes.
> >Somehow both sdb and sdb3 have a superblock for the same array. Must have
> >been a typo somewhere I suspect.
> >You should remove the one you don't want:
>
> > mdadm --zero-superblock /dev/sdb
>
> >then it should all work nicely again.
>
>
> Unfortunately, the above command gave the following error :
>
> root@server2:~# mdadm --zero-superblock /dev/sdb
> mdadm: Couldn't open /dev/sdb for write - not zeroing
>
> Do you know how to work around?
Presumably this is because sdb3 is active in the array. This keeps sdb busy.
If this is the current situation then adding --force to the command should
make it work.
Otherwise you might need to remove sdb from the array first.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-02-20 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 4:11 Problem rebuild raid 1 replacement disk RANSOM, Tony
2012-02-20 5:29 ` NeilBrown
2012-02-20 8:28 ` RANSOM, Tony
2012-02-20 9:11 ` NeilBrown
2012-02-20 9:15 ` RANSOM, Tony
2012-02-20 10:51 ` NeilBrown [this message]
2012-02-20 12:18 ` RANSOM, Tony
2012-02-21 10:09 ` RANSOM, Tony
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=20120220215147.7684efda@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=tony.ransom@baesystems.com \
/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