From: "H. Peter Anvin" <hpa@zytor.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Neil Brown <neilb@suse.de>,
Peter Rabbitson <rabbit+list@rabbit.us>,
linux-raid@vger.kernel.org
Subject: Re: Proper partition type for components with V1.x superblocks?
Date: Mon, 07 Jul 2008 10:33:08 -0700 [thread overview]
Message-ID: <48725354.1070900@zytor.com> (raw)
In-Reply-To: <1215439360.14196.17.camel@firewall.xsintricity.com>
Doug Ledford wrote:
>
> The same is true of version 0.90.0 superblocks. It was probably a bad
> decision to make raid1 arrays mountable as normal filesystems in
> hindsight, but it did ease a lot of things at the time (like booting
> from a raid1 device using lilo, the only boot loader back in the day).
> In any case, given the number of existing 0.90.0 and 1.0 superblock
> systems out there, any install code that doesn't look for them is just
> flat deficient. So I can see your point from the stand point of wanting
> to correct a past mistake, but the flip side of the coin is that even if
> you do such a thing, any installer will still be buggy and broken for
> many years to come if it doesn't check for raid superblocks before
> treating a filesystem like a normal filesystem.
>
It certainly helps bootloaders wanting to boot off RAID-1. 1.2
superblocks, at the beginning but with an offset, are fine for that
purpose too, but requires special handling.
-hpa
next prev parent reply other threads:[~2008-07-07 17:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:26 Proper partition type for components with V1.x superblocks? Peter Rabbitson
2008-06-11 11:23 ` Andre Noll
2008-06-11 12:12 ` Peter Rabbitson
2008-06-11 21:06 ` Andre Noll
2008-06-11 11:24 ` David Greaves
2008-06-11 11:35 ` Peter Rabbitson
2008-06-11 23:52 ` Neil Brown
2008-07-02 22:02 ` H. Peter Anvin
2008-07-03 5:17 ` Doug Ledford
2008-07-07 3:17 ` Neil Brown
2008-07-07 14:02 ` Doug Ledford
2008-07-07 17:33 ` H. Peter Anvin [this message]
2008-07-07 17:32 ` H. Peter Anvin
2008-07-07 23:10 ` David Greaves
2008-07-07 23:47 ` H. Peter Anvin
2008-07-07 17:38 ` 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=48725354.1070900@zytor.com \
--to=hpa@zytor.com \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rabbit+list@rabbit.us \
/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.