linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Jan Ceuleers <jan.ceuleers@computer.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Spares Missing event in case of spare group?
Date: Fri, 15 May 2009 14:38:21 +1000	[thread overview]
Message-ID: <18956.61885.121354.537078@notabene.brown> (raw)
In-Reply-To: message from Jan Ceuleers on Friday May 1

On Friday May 1, jan.ceuleers@computer.org wrote:
> Jan Ceuleers wrote:
> > NeilBrown wrote:
> >> Yes.  Remove the "spares=1" from each line.
> >> The sole effect of this text is to tell --monitor to expect a spare, and
> >> to complain if no spare is found.
> > 
> > Many thanks. I hadn't picked that up from the manpage, so here is a 
> > patch for your consideration:
> 
> Reasonable patch?

Yes.  Thanks.  (And sorry for the delay :-)

NeilBrown

> 
> > diff --git a/mdadm.conf.5 b/mdadm.conf.5
> > index 40295be..b67bec4 100644
> > --- a/mdadm.conf.5
> > +++ b/mdadm.conf.5
> > @@ -135,6 +135,7 @@ this is mainly for compatibility with the output of
> >  .TP
> >  .B spares=
> >  The value is a number of spare devices to expect the array to have.
> > +The sole use of this keyword and value is as follows:
> >  .B mdadm \-\-monitor
> >  will report an array if it is found to have fewer than this number of
> >  spares when
> 
> Thanks, Jan
> --
> 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:[~2009-05-15  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 16:02 Spares Missing event in case of spare group? Jan Ceuleers
2009-04-19 20:39 ` NeilBrown
2009-04-20 19:02   ` Jan Ceuleers
2009-05-01  6:53     ` Jan Ceuleers
2009-05-15  4:38       ` 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=18956.61885.121354.537078@notabene.brown \
    --to=neilb@suse.de \
    --cc=jan.ceuleers@computer.org \
    --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).