From: Chris Webb <chris@arachsys.com>
To: Neil Brown <neilb@suse.de>
Cc: Andre Noll <maan@systemlinux.org>,
Doug Ledford <dledford@redhat.com>,
Matthias Urlichs <matthias@urlichs.de>,
linux-raid@vger.kernel.org
Subject: Re: RAID1 assembled broken array
Date: Fri, 25 Sep 2009 11:42:19 +0100 [thread overview]
Message-ID: <20090925104219.GG26094@arachsys.com> (raw)
In-Reply-To: <19132.31575.349988.442763@notabene.brown>
Neil Brown <neilb@suse.de> writes:
> On Thursday September 17, maan@systemlinux.org wrote:
>
> > BTW: Why are new arrays still created with 0.90 metadata format by
> > default?
>
> Because I'm a chicken....
>
> I guess it probably is time ... but to we make the default 1.0, which
> is compatible with people's expectations, to 1.1 which is generally a
> safer approach (you cannot mount a bare device by mistake).
One problem with 1.x metadata formats is that you can't assemble them at
boot time without building an initrd/initramfs containing userspace to put
them together. An md=0,xxx kernel argument only appears to work for 0.90
superblocks. (Would you accept a patch to fix this; it doesn't feel like it
should be particularly hard?)
Another issue with 1.1 and 1.2 metadata is that you can't make a mirror out
of sd*, install a bootloader (e.g. extlinux) on the md, and then boot the
corresponding system. That said, I guess it wouldn't be hard to make a
little 'mbr' that understands the data offset in the md 1.2 container, so if
I'm honest, it's just laziness that keeps me using 0.90 where it works out
of the box without the need to hack any bootloader code or create untidy
partitions just for booting.
Best wishes,
Chris.
next prev parent reply other threads:[~2009-09-25 10:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 19:22 RAID1 assembled broken array Matthias Urlichs
2009-09-15 19:24 ` Majed B.
2009-09-15 19:33 ` Matthias Urlichs
2009-09-15 19:43 ` Majed B.
2009-09-15 20:04 ` Doug Ledford
2009-09-15 20:00 ` Doug Ledford
2009-09-15 20:27 ` Matthias Urlichs
2009-09-15 21:01 ` NeilBrown
2009-09-16 4:50 ` Matthias Urlichs
2009-09-17 16:44 ` Doug Ledford
2009-09-17 17:09 ` Matthias Urlichs
2009-09-17 17:12 ` Majed B.
2009-09-25 8:07 ` Neil Brown
2009-09-17 8:25 ` Andre Noll
2009-09-25 8:12 ` Neil Brown
2009-09-25 10:42 ` Chris Webb [this message]
2009-09-26 9:58 ` Andre Noll
2009-09-26 13:01 ` John Robinson
2009-09-26 19:21 ` Clinton Lee Taylor
2009-09-28 16:12 ` Andre Noll
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=20090925104219.GG26094@arachsys.com \
--to=chris@arachsys.com \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=maan@systemlinux.org \
--cc=matthias@urlichs.de \
--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).