From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: Bug report: mdadm -E oddity
Date: Sun, 15 May 2005 19:32:01 +0200 [thread overview]
Message-ID: <20050515173200.GA20966@percy.comedia.it> (raw)
In-Reply-To: <1116077316.13780.52.camel@compaq-rhel4.xsintricity.com>
i would like to add some comments
On Sat, May 14, 2005 at 09:28:35AM -0400, Doug Ledford wrote:
>Actually, what I'm working on is Fedora Core 4 and the boot up sequence.
>Specifically, I'm trying to get the use of mdadm -As acceptable as the
hint, mdassemble :)
>So, here's some of the feedback I've gotten about this and the
>constraints I'm working under as a result:
initrd should be used to mount root filesystem, handling other stuff in
initrd is just asking for more trouble
> 1. People don't want to remake initrd images and update mdadm.conf
> files with every raid change. So, the scan facility needs to
> properly handled unknown arrays (it doesn't currently).
do really people change the UUID of the array containing / that often?
> 2. People don't want to have a degraded array not get started (this
> isn't a problem as far as I can tell).
what would be the issue causing this.
> 3. Udev throws some kinks in things because the raid startup is
i run udevstart in initrd after loading modules and before
assembling md's. if nash was a better shell, i could use udev
instead of udevstart
> have completed). However, with the advent of stacked md
mdadm should create device files for md arrays if you ask it to,
is this what you are after or are there other issues
> 4. Currently, the default number of partitions on a partitionable
....
> numbers relative to how the array was created. I would suggest
> encoding this somewhere in the superblock and then setting this
> to 0 on normal arrays and non-0 for partitionable arrays and
> that becomes your flag that determines whether an array is
> partitionable.
agreed
> 5. I would like to be able to support dynamic multipath in the
> initrd image. In order to do this properly, I need the ability
i don't like using fc for boot disks, so i never tried, and i'll just
shut up.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2005-05-15 17:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 15:44 Bug report: mdadm -E oddity Doug Ledford
2005-05-13 17:11 ` Doug Ledford
2005-05-13 23:01 ` Neil Brown
2005-05-14 13:28 ` Doug Ledford
2005-05-15 17:32 ` Luca Berra [this message]
2005-05-20 7:00 ` Neil Brown
2005-05-20 12:30 ` Doug Ledford
2005-05-20 16:04 ` Paul Clements
2005-05-20 17:16 ` Peter T. Breuer
2005-05-20 18:40 ` Doug Ledford
2005-05-20 19:15 ` Peter T. Breuer
2005-05-20 21:31 ` Doug Ledford
2005-05-20 17:45 ` Doug Ledford
2005-05-20 18:33 ` Peter T. Breuer
2005-05-20 20:01 ` berk walker
2005-05-20 21:00 ` Gil
2005-05-20 21:51 ` Peter T. Breuer
2005-05-20 22:14 ` berk walker
2005-05-20 20:05 ` Paul Clements
2005-05-16 16:46 ` Doug Ledford
2005-05-20 7:08 ` Neil Brown
2005-05-20 11:29 ` Doug Ledford
2005-05-16 22:11 ` Doug Ledford
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=20050515173200.GA20966@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).