From: Pete Zaitcev <zaitcev@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: schwidefsky@de.ibm.com, viro@parcelfarce.linux.theplanet.co.uk,
linux-kernel@vger.kernel.org, zaitcev@redhat.com,
<neilb@cse.unsw.edu.au>
Subject: Re: Patch to add RAID autostart to IBM partitions
Date: Sat, 16 Oct 2004 08:29:37 -0700 [thread overview]
Message-ID: <20041016082937.62c15e6c@lembas.zaitcev.lan> (raw)
In-Reply-To: <20041016110939.GB30336@infradead.org>
On Sat, 16 Oct 2004 12:09:39 +0100
Christoph Hellwig <hch@infradead.org> wrote:
> We had this for a few partition types (and full block devices) already
> and it's been vetoed. Use mdadm from initrd/initramfs instead.
It is doable in theory, but in practice mdadm is too retarded (I'm taliking
about mdadm 1.6.0 here). Its man page says:
mdadm can perform (almost) all of its functions without having a
configuration file and does not use one by default.
I guess "almost" is the key. Firstly, it collapses with any attempt to run
"mdadm -A -s" or any variation of such, because it's full of places like
this.
mddev_ident_t array_ident = conf_get_ident(configfile, dv->devname);
mdfd = open_mddev(dv->devname, array_ident->autof);
Obviously, array_ident is NULL if a config file is not present. It is
possible to fool the stupid thing by giving it a dummy config file,
like this one:
DEVICE partitions
ARRAY /dev/md0
It still won't scan, aborting with this:
mdadm: /dev/dasda has no superblock - assembly aborted
The ChangeLog looks as if someone tried to make it work, but I observe
it didn't go very far.
-- Pete
next prev parent reply other threads:[~2004-10-16 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 5:48 Pete Zaitcev
2004-10-16 11:09 ` Christoph Hellwig
2004-10-16 15:29 ` Pete Zaitcev [this message]
2004-10-19 1:54 ` Neil Brown
2004-10-19 16:32 ` Pete Zaitcev
2004-10-29 2:16 ` 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=20041016082937.62c15e6c@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=schwidefsky@de.ibm.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®