linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linas <linas@austin.ibm.com>
Cc: Jason Lunz <lunz@falooley.org>,
	neilb@suse.de, linux-hotplug-devel@lists.sourceforge.net,
	linux-raid@vger.kernel.org
Subject: Re: 2.6.15: mdrun, udev -- who creates nodes?
Date: Tue, 31 Jan 2006 22:44:13 +0100	[thread overview]
Message-ID: <20060131214413.GF4335@percy.comedia.it> (raw)
In-Reply-To: <20060131192643.GU19465@austin.ibm.com>

On Tue, Jan 31, 2006 at 01:26:43PM -0600, linas wrote:
>On Tue, Jan 31, 2006 at 04:40:46PM +0000, Jason Lunz was heard to remark:
>> md@Linux.IT said:
>> >> -- kernel scans /dev/hda1, looking for md superblock
>> >> -- kernel assembles devices according to info found in the superblocks
>> >> -- udev creates /dev/md0, etc.=20
>> > The problem is that some users and distributions build the drivers as
>> > modules and/or disable in-kernel auto-assembly.
>> 
>> Not only that, the raid developers themselves consider autoassembly
>> deprecated.
>> 
>> http://article.gmane.org/gmane.linux.kernel/373620
>
>Hmm. My knee-jerk, didn't-stop-to-think-about-it reaction is that 
>this is one of the finest features of linux raid, so why remove it?

please, no, not again:
this particular horse has been beaten to death many times before.

the in kernel auto assembly should be removed for good (read the
linux-raid list archive to understand why)

it should be replaced by auto assembly in user space (mdadm), which does
not suffer from the problems that in-kernel has. neither it does suffer
from a poor configuration file like the (unmaintained) raidtools had.
and is much more cleaner and maintainable.

L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  parent reply	other threads:[~2006-01-31 21:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43DCA9CA.5020505@bl.com>
     [not found] ` <20060129123532.GA6158@wonderland.linux.it>
     [not found]   ` <43DCD614.20705@pobox.com>
     [not found]     ` <20060130204231.GP19465@austin.ibm.com>
     [not found]       ` <20060130204743.GA13902@wonderland.linux.it>
     [not found]         ` <dro3ue$ntb$1@sea.gmane.org>
2006-01-31 19:26           ` 2.6.15: mdrun, udev -- who creates nodes? linas
2006-01-31 20:19             ` Molle Bestefich
2006-01-31 20:52               ` Jason Lunz
2006-01-31 21:13                 ` linas
2006-01-31 21:58                   ` Molle Bestefich
2006-02-01  9:27                     ` Andy Smith
2006-02-01 19:44                       ` Luca Berra
2006-02-01 22:14                         ` Andy Smith
2006-02-02  1:27                       ` Neil Brown
2006-01-31 21:44             ` Luca Berra [this message]
2006-02-10 22:46             ` Bill Davidsen

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=20060131214413.GF4335@percy.comedia.it \
    --to=bluca@comedia.it \
    --cc=linas@austin.ibm.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=lunz@falooley.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 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).