linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Martin Cracauer <cracauer@cons.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Superblock V 1.2
Date: Tue, 09 Nov 2010 17:08:49 +0000	[thread overview]
Message-ID: <4CD98021.2060501@anonymous.org.uk> (raw)
In-Reply-To: <20101109163512.GA15649@cons.org>

On 09/11/2010 16:35, Martin Cracauer wrote:
> John Robinson wrote on Sun, Nov 07, 2010 at 09:39:03PM +0000:
[...]
>> That's the other difference between 0.90 and 1.x metadata. In-kernel
>> auto-assembly is only available for 0.90, and Neil Brown has made it
>> clear that there will never be in-kernel auto-assembly for 1.x, and
>> explained at length why. You need mdadm to start 1.x arrays, in your
>> initrd if your root filesystem is on such an array. All modern distros
>> create suitable initrds automatically. We are moving towards having
>> array assembly handled by udev invoking mdadm as devices are discovered.
>
> That's good it know.  I still think that udev is a plot to destroy
> Linux as we know it so I guess I'm gonna recreate this particular
>   array :-)
>
> What do you do if you plug in a couple harddrives that have arrays on
> them that you do not want assembled? Right now you just set them to a
> partition type other than autodetect and you are good.

You can still do that, but the "right" way to do it (I think) is to use 
the AUTO keyword and only to include the arrays you want assembled at 
boot time in the mdadm.conf that goes into the initrd.

> What do you do when udev maintainers in distributions screw up and
> replace good udev entires with bad ones? That happened to me
> repeatedly and is the major reason for the attitude above.

Oh dear, you've had a bad experience there then. I like udev. I disliked 
the old huge /dev with gazillions of entries for devices you don't have, 
and you still ended up using MAKEDEV or mknod whenever you added 
something new. I did say "moving towards" because udev-based assembly 
isn't 100% there yet, and I don't think any distros are trying to use 
it. But the other great thing we will get with udev is hotplugging, 
including the option to configure in advance auto-rebuilding of arrays, 
something that hardware RAID adapters have always had but we still don't 
for software RAID.

Cheers,

John.

  reply	other threads:[~2010-11-09 17:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07 19:15 Superblock V 1.2 Martin Cracauer
2010-11-07 21:03 ` Leslie Rhorer
2010-11-07 21:08   ` Martin Cracauer
2010-11-07 21:39     ` John Robinson
2010-11-09 16:35       ` Martin Cracauer
2010-11-09 17:08         ` John Robinson [this message]
2010-11-15  1:11           ` Neil Brown
2010-11-15 16:16             ` Martin Cracauer
2010-11-15 19:47               ` Neil Brown
2010-11-15 19:52                 ` Martin Cracauer
2010-11-15 20:11                   ` 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=4CD98021.2060501@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=cracauer@cons.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).