From: "JaniD++" <djani22@dynamicweb.hu>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: where is the spare drive? :-)
Date: Thu, 12 Jan 2006 10:11:52 +0100 [thread overview]
Message-ID: <004f01c61758$42a5f090$a400a8c0@dcccs> (raw)
In-Reply-To: 17349.51157.745149.135889@cse.unsw.edu.au
----- Original Message -----
From: "Neil Brown" <neilb@suse.de>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-raid@vger.kernel.org>
Sent: Thursday, January 12, 2006 4:07 AM
Subject: Re: where is the spare drive? :-)
> On Monday January 2, djani22@dynamicweb.hu wrote:
> >
> > 5. The question
> >
> > Why shows sdh2 as spare?
> > The MD array size is correct.
> > And i really can see, the all drive is reading, and sdh2 is *ONLY*
writing.
> >
>
> man mdadm
>
> Towards the end of the CREATE MODE section:
>
> When creating a RAID5 array, mdadm will automatically create a
degraded
> array with an extra spare drive. This is because building the
spare
> into a degraded array is in general faster than resyncing the
parity on
> a non-degraded, but not clean, array. This feature can be
over-ridden
> with the --force option.
>
>
> I hope this clarifies the situation.
>
> NeilBrown
Ahh, this was avoid my attention.
The mdadm man page (and functionallity) is quite large.
I think this is more important to let some people to overwrite own data.
I think it is neccessary to place some note to the man page to warn people
about this exception.
Anyway this is a good idea! :-)
Thanks to note me about this.
Cheers,
Janos
>
> -
> 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
prev parent reply other threads:[~2006-01-12 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 23:26 where is the spare drive? :-) JaniD++
2006-01-05 6:16 ` Marc
2006-01-05 11:06 ` JaniD++
2006-01-12 3:07 ` Neil Brown
2006-01-12 9:11 ` JaniD++ [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='004f01c61758$42a5f090$a400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--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.