All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Neil Brown <neilb@suse.de>,
	linux-raid@vger.kernel.org, klibc list <klibc@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [klibc] Re: Exporting which partitions to md-configure
Date: Tue, 7 Feb 2006 11:43:11 +0100	[thread overview]
Message-ID: <20060207104311.GD22221@percy.comedia.it> (raw)
In-Reply-To: <43E80A5A.5040002@zytor.com>

On Mon, Feb 06, 2006 at 06:47:54PM -0800, H. Peter Anvin wrote:
>Neil Brown wrote:
>Requiring that mdadm.conf describes the actual state of all volumes 
>would be an enormous step in the wrong direction.  Right now, the Linux 
>md system can handle some very oddball hardware changes (such as on 
>hera.kernel.org, when the disks not just completely changed names due to 
>a controller change, but changed from hd* to sd*!)
DEVICE partitions
ARRAY /dev/md0 UUID=xxyy:zzyy:aabb:ccdd

would catch that


>Dynamicity is a good thing, although it needs to be harnessed.
>
> > kernel parameter md_root_uuid=xxyy:zzyy:aabb:ccdd...
> >    This could be interpreted by an initramfs script to run mdadm
> >    to find and assemble the array with that uuid.  The uuid of
> >    each array is reasonably unique.
I could change mdassemble to allow accepting an uuid on the command line
and assemble a /dev/md0 with the specified uuid (at the moment it only
accepts a configuration file, which i tought was enough for
initrd/initramfs.

>This, in fact is *EXACTLY* what we're talking about; it does require 
>autoassemble.  Why do we care about the partition types at all?  The 
>reason is that since the md superblock is at the end, it doesn't get 
>automatically wiped if the partition is used as a raw filesystem, and so 
>it's important that there is a qualifier for it.
I don't like using partition type as a qualifier, there is people who do
not wish to partition their drives, there are systems not supporting
msdos like partitions, heck even m$ is migrating away from those.

In any case if that has to be done it should be done into mdadm, not
in a different scrip that is going to call mdadm (behaviour should be
consistent between mdadm invoked by initramfs and mdadm invoked on a
running system).

If the user wants to reutilize a device that was previously a member of
an md array he/she should use mdadm --zero-superblock to remove the
superblock.
I see no point in having a system that tries to compensate for users not
following correct procedures. sorry.

L.

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

  parent reply	other threads:[~2006-02-07 10:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  0:52 Exporting which partitions to md-configure H. Peter Anvin
2006-01-31  1:10 ` Neil Brown
2006-01-31  1:42   ` H. Peter Anvin
2006-01-31  2:01     ` Neil Brown
2006-01-31  2:05       ` H. Peter Anvin
2006-02-06  1:46         ` Neil Brown
2006-02-06  3:29           ` Kyle Moffett
2006-02-07  2:47           ` [klibc] " H. Peter Anvin
2006-02-07  9:03             ` Neil Brown
2006-02-07 10:43             ` Luca Berra [this message]
2006-02-07 15:46               ` H. Peter Anvin
2006-02-07 16:47                 ` Luca Berra
2006-02-07 16:55                   ` H. Peter Anvin
2006-02-07 17:03                     ` Luca Berra
2006-01-31  6:49     ` Chris Wedgwood
2006-01-31  1:43   ` Kyle Moffett
2006-01-31  1:45     ` H. Peter Anvin
2006-01-31  2:01     ` Neil Brown
2006-01-31  2:38       ` H. Peter Anvin
2006-01-31  6:42       ` Kyle Moffett
2006-01-31  3:21 ` [klibc] " Greg KH
2006-01-31  3:24   ` Greg KH
2006-01-31  6:53     ` Kyle Moffett
2006-01-31  3:53   ` H. Peter Anvin

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=20060207104311.GD22221@percy.comedia.it \
    --to=bluca@comedia.it \
    --cc=hpa@zytor.com \
    --cc=klibc@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.