From: NeilBrown <neilb@suse.de>
To: Jes.Sorensen@redhat.com
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/1] Make failure message on re-add more explcit
Date: Thu, 23 Feb 2012 09:04:12 +1100 [thread overview]
Message-ID: <20120223090412.2b14fb7f@notabene.brown> (raw)
In-Reply-To: <1329930000-20679-1-git-send-email-Jes.Sorensen@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Wed, 22 Feb 2012 17:59:59 +0100 Jes.Sorensen@redhat.com wrote:
> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> Hi,
>
> I have seen this come up on the list a couple of times, and also had
> bugs filed over it, since this used to 'work'. Making the printed
> error message a little more explicit should hopefully make it clearer
> why this is being rejected.
>
> Thoughts?
While I'm always happy to make the error messages more helpful, I don't think
this one does :-(
The reason for the change was that people seemed to often use "--add" when
what they really wanted was "--re-add".
--add will try --re-add first, but it if that doesn't succeed it would do the
plain add and destroy the metadata.
So I introduced the requirement that if you want to destroy metadata, you
need to do it explicitly (and I know that won't stop people, but hopefully it
will slow them down).
Also, this is not at all specific to raid1 - it applies equally to
raid4/5/6/10.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-02-22 22:04 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 ` NeilBrown [this message]
2012-02-22 23:16 ` [PATCH 0/1] Make failure message on re-add more explcit Jes Sorensen
2012-02-23 1:57 ` John Robinson
2012-02-23 8:34 ` Jes Sorensen
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=20120223090412.2b14fb7f@notabene.brown \
--to=neilb@suse.de \
--cc=Jes.Sorensen@redhat.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;
as well as URLs for NNTP newsgroup(s).