linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Andre Majorel <aym-xunil@teaser.fr>
Cc: linux-raid@vger.kernel.org
Subject: Re: Man page patch (manage mode options clarification)
Date: Fri, 13 Jul 2007 15:41:51 +1000	[thread overview]
Message-ID: <18071.4255.138632.190115@notabene.brown> (raw)
In-Reply-To: message from Andre Majorel on Sunday January 14

On Sunday January 14, aym-xunil@teaser.fr wrote:
> This one is more debatable than the previous one. It attempts to
> clarify the synopses of the manage mode options.
> 
> Those options take arguments so make that evident in the synopses.
> 
> I'm not entirely sure about the wording. Comments welcome. Is it
> clearer than what we have now ?

I don't like it, though it is very possibly that the current text
could be improved.

I don't see the devices as arguments to the flags.  They are arguments
to "mdadm" and the flag say what it should do with the arguments.

Maybe it is a subtle difference.  Maybe I just need more people to say
"Neil is wrong, Andre is right"...  Maybe someone else will have an
even better idea....

Thanks anyway.

NeilBrown


> 
> Before :
> 
>   For Manage mode:
>      -a, --add
>             hot-add listed devices.
> 
>      --re-add
>             re-add a device that was recently removed from an array.
> 
>      -r, --remove
>             remove  listed  devices.  They must not be active.  i.e.
>             they should be failed or spare devices.
> 
>      -f, --fail
>             mark listed devices as faulty.
> 
>      --set-faulty
>             same as --fail.
> 
> After :
> 
>   For Manage mode:
>      -a, --add [component-device ...]
>             Hot-add  its  arguments to raid-device.  If no arguments
>             are given, this option is a no-op.
> 
>      --re-add [component-device ...]
>             Re-add its arguments to raid-device.  The arguments must
>             be  devices  that  were recently removed from the array.
>             If no arguments are given, this option is a no-op.
> 
>      -r, --remove [component-device ...]
>             Remove its arguments from  raid-device.   The  arguments
>             must  not be active, i.e. they should be failed or spare
>             devices.  If no arguments are given, this  option  is  a
>             no-op.
> 
>      -f, --fail [component-device ...]
>             Mark  its  arguments  as  faulty.   If  no arguments are
>             given, this option is a no-op.
> 
>      --set-faulty [component-device ...]
>             Same as --fail.
> 
> -- 
> André Majorel <URL:http://www.teaser.fr/~amajorel/>
> Do not use this account for regular correspondence.
> See the URL above for contact information.
> diff -ur mdadm-2.6-man1/mdadm.8 mdadm-2.6-man2/mdadm.8
> --- mdadm-2.6-man1/mdadm.8	2007-01-14 14:50:25.000000000 +0100
> +++ mdadm-2.6-man2/mdadm.8	2007-01-14 15:19:07.000000000 +0100
> @@ -13,7 +13,7 @@
>  
>  .SH SYNOPSIS
>  
> -.BI mdadm " [mode] <raiddevice> [options] <component-devices>"
> +.BI mdadm " [mode] <raid-device> [options] <component-devices>"
>  
>  .SH DESCRIPTION
>  RAID devices are virtual devices created from two or more
> @@ -836,25 +836,30 @@
>  .SH For Manage mode:
>  
>  .TP
> -.BR -a ", " --add
> -hot-add listed devices.
> +\fB\-a\fP, \fB\-\-add\fP [\fIcomponent-device\fP ...]
> +Hot-add its arguments to \fIraid-device\fP.
> +If no arguments are given, this option is a no-op.
>  
>  .TP
> -.BR --re-add
> -re-add a device that was recently removed from an array.
> +\fB\-\-re\-add\fP [\fIcomponent-device\fP ...]
> +Re-add its arguments to \fIraid-device\fP.
> +The arguments must be devices that were recently removed from the array.
> +If no arguments are given, this option is a no-op.
>  
>  .TP
> -.BR -r ", " --remove
> -remove listed devices.  They must not be active.  i.e. they should
> -be failed or spare devices.
> +\fB\-r\fP, \fB\-\-remove\fP [\fIcomponent-device\fP ...]
> +Remove its arguments from \fIraid-device\fP.
> +The arguments must not be active, i.e. they should be failed or spare devices.
> +If no arguments are given, this option is a no-op.
>  
>  .TP
> -.BR -f ", " --fail
> -mark listed devices as faulty.
> +\fB\-f\fP, \fB\-\-fail\fP [\fIcomponent-device\fP ...]
> +Mark its arguments as faulty.
> +If no arguments are given, this option is a no-op.
>  
>  .TP
> -.BR --set-faulty
> -same as --fail.
> +\fB\-\-set\-faulty\fP [\fIcomponent-device\fP ...]
> +Same as \fB\-\-fail\fP.
>  
>  .P
>  Each of these options require that the first device list is the array
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2007-07-13  5:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 20:21 Man page patch (manage mode options clarification) Andre Majorel
2007-07-13  5:41 ` Neil Brown [this message]

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=18071.4255.138632.190115@notabene.brown \
    --to=neilb@suse.de \
    --cc=aym-xunil@teaser.fr \
    --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).