From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/1] Make failure message on re-add more explcit
Date: Thu, 23 Feb 2012 09:34:34 +0100 [thread overview]
Message-ID: <4F45FA1A.2020706@redhat.com> (raw)
In-Reply-To: <4F459D05.5060104@anonymous.org.uk>
On 02/23/12 02:57, John Robinson wrote:
> On 22/02/2012 23:16, Jes Sorensen wrote:
> [...]
>> The goal was to try and reduce the number of bug reports over this by
>> making it more obvious/explicit, so if you have a suggestion for how to
>> do so in a better way, I am all game.
>
> How about:
>
> mdadm /dev/md0 --add %s
> : %s was already a member of /dev/md0, attempting re-add
> : Re-add failed because <reason>
> : Not performing add as that would zero the superblock on %s and make it
> a spare
> : mdadm --add used to do that automatically but it was potentially
> dangerous
> : If that is what you really want to do, use mdadm --zero-superblock %s
> first.
>
This would get my vote, way better than my messy attempt.
Cheers,
Jes
next prev parent reply other threads:[~2012-02-23 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 16:59 [PATCH 0/1] Make failure message on re-add more explcit Jes.Sorensen
2012-02-22 17:00 ` [PATCH 1/1] Make error message on failure to --re-add more explicit Jes.Sorensen
2012-02-22 22:04 ` [PATCH 0/1] Make failure message on re-add more explcit NeilBrown
2012-02-22 23:16 ` Jes Sorensen
2012-02-23 1:57 ` John Robinson
2012-02-23 8:34 ` Jes Sorensen [this message]
2012-02-23 8:47 ` J. Ali Harlow
2012-02-27 0:01 ` NeilBrown
2012-04-05 18:59 ` Doug Ledford
2012-04-09 23:41 ` NeilBrown
2012-04-10 23:44 ` Doug Ledford
2012-04-18 4:25 ` NeilBrown
2012-04-23 19:36 ` Doug Ledford
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=4F45FA1A.2020706@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.