linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: David Greaves <david@dgreaves.com>,
	Bryan Christ <bryan.christ@hp.com>,
	Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-raid@vger.kernel.org
Subject: Re: Raid array is not automatically detected.
Date: Thu, 19 Jul 2007 09:09:39 +1000	[thread overview]
Message-ID: <18078.40371.650807.535202@notabene.brown> (raw)
In-Reply-To: message from Bill Davidsen on Wednesday July 18

On Wednesday July 18, davidsen@tmr.com wrote:
> David Greaves wrote:
> >
> > See where it says 'component' ? :)
> >
> > I wish mdadm --detail and --examine were just aliases and the output 
> > varied according to whether you looked at a component (eg /dev/sda1) 
> > or an md device (/dev/md0)
> >
> > I get that wrong *all* the time...
> 
> Neil, if you will take that as a suggestion, you can take this as a 
> second. While I have learned to use the correct option most of the time, 
> this is a case where the software can make an unambiguous decision to 
> avoid the human having to stop and think which option is appropriate.

The software cannot make an unambiguous decision. It is quite possible
for one md device to be a component of another md device.  In that
case, --examine and --detail are both very meaningful and very
different.

If you have trouble remembering the difference, train yourself to use
--query instead.

I am willing to consider suggestions for improving the error message
when -D or -E don't find what they expect.
I am willing to add aliases that might make it easier to remember the
difference (I confess that I chose 'detail' and 'examine' largely
because they start with 'd' and 'e', to go with assemble, build, and
create)
I am willing to make --query more useful if anyone has any
suggestions.
But I am not willing to make --detail and --examine behave
identically.

NeilBrown

  reply	other threads:[~2007-07-18 23:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 20:36 Raid array is not automatically detected Bryan Christ
2007-07-14  0:03 ` Zivago Lee
2007-07-14  2:09   ` Bryan Christ
2007-07-14 13:51 ` Bill Davidsen
2007-07-14 13:53   ` Justin Piszcz
2007-07-14 17:10     ` Bill Davidsen
2007-07-14 17:08       ` Justin Piszcz
2007-07-16 14:19     ` Bryan Christ
2007-07-16 15:21       ` David Greaves
2007-07-18  5:28         ` dean gaudet
2007-07-18  8:06           ` Justin Piszcz
2007-07-18  8:52           ` David Greaves
2007-07-18 14:39         ` Bryan Christ
2007-07-18 15:46           ` David Greaves
2007-07-18 15:49             ` Bryan Christ
2007-07-18 18:56             ` Bill Davidsen
2007-07-18 23:09               ` Neil Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-17 15:07 Daniel Reichelt
2008-10-17 18:40 ` Bryan Christ

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=18078.40371.650807.535202@notabene.brown \
    --to=neilb@suse.de \
    --cc=bryan.christ@hp.com \
    --cc=david@dgreaves.com \
    --cc=davidsen@tmr.com \
    --cc=jpiszcz@lucidpixels.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).