From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 kicks non-fresh drives
Date: Sat, 27 May 2006 14:21:13 +0200 [thread overview]
Message-ID: <20060527122113.GI8203@percy.comedia.it> (raw)
In-Reply-To: <Pine.LNX.4.44.0605261533090.20378-100000@coffee.psychology.mcmaster.ca>
On Fri, May 26, 2006 at 03:37:29PM -0400, Mark Hahn wrote:
>> i strongly believe it is not correct to let kernel auto-assemble devices
>> kernel auto-assembly should be disable and activation should be handled
>> by mdadm only!
>
>it's a convenience/safety tradeoff, like so many other cases.
>without kernel auto-assembly, it's somewhat more annoying to
>boot onto MD raid, right? you are forced to put MD config stuff
>into your initrd, etc.
yes, it is, but initrd are generated by scripts nowadays, so you wont
even notice.
>I don't see why auto-assembly is such a bad thing. it means you
please read the list archives, it has been explained to boredom
>the only argument I see against (kernel) auto-assembly is the
>general principle of moving things out of the kernel where possible.
>but that's not a hard/fast rule anyway, so...
please read the list archives, it has been explained to boredom
Regards,
L.
and please,
do not To: or Cc: me, i do actively read the list.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2006-05-27 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 15:38 RAID5 kicks non-fresh drives Craig Hollabaugh
2006-05-25 21:18 ` Neil Brown
2006-05-25 21:39 ` Craig Hollabaugh
2006-05-25 22:30 ` Craig Hollabaugh
2006-05-26 7:57 ` Mikael Abrahamsson
2006-05-26 14:11 ` Craig Hollabaugh
2006-05-26 16:45 ` Mark Hahn
2006-05-26 17:06 ` Craig Hollabaugh
2006-05-26 17:30 ` Mark Hahn
2006-05-26 18:01 ` Craig Hollabaugh
2006-05-26 18:38 ` Luca Berra
2006-05-26 19:37 ` Mark Hahn
2006-05-27 12:21 ` Luca Berra [this message]
2006-05-29 4:34 ` Neil Brown
2006-05-26 17:32 ` Bill Davidsen
2006-05-26 17:49 ` Craig Hollabaugh
2006-05-29 5:20 ` Neil Brown
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=20060527122113.GI8203@percy.comedia.it \
--to=bluca@comedia.it \
--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).