linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Southerwood <ts@dionic.net>
To: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Use new sb type
Date: Tue, 29 Jan 2008 04:09:02 +0000	[thread overview]
Message-ID: <479EA6DE.9070503@dionic.net> (raw)
In-Reply-To: <479E2DDA.5040102@dgreaves.com>

David Greaves wrote:
> Peter Rabbitson wrote:
>> David Greaves wrote:
>>> Jan Engelhardt wrote:
>>>> This makes 1.0 the default sb type for new arrays.
>>>>
>>> IIRC there was a discussion a while back on renaming mdadm options
>>> (google "Time
>>> to  deprecate old RAID formats?") and the superblocks to emphasise the
>>> location
>>> and data structure. Would it be good to introduce the new names at the
>>> same time
>>> as changing the default format/on-disk-location?
>>>
>>> David
>> Also wasn't the concession to make 1.1 default instead of 1.0 ?
>>
> IIRC Doug Leford did some digging wrt lilo + grub and found that 1.1 and 1.2
> wouldn't work with them. I'd have to review the thread though...
> 
> David
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

For what it's worth, that was my finding too. -e 0.9+1.0 are fine with
GRUB, but  1.1 an 1.2 won't work under the filesystem that contains
/boot, at least with GRUB 1.x (I haven't used LILO for some time nor
have I tried the development GRUB 2).

The reason IIRC boils down to the fact that GRUB 1 isn't MD aware, and
the only reason one can "get away" with using it on a RAID 1 setup at
all is that the constituent devices present the same data as the
composite MD device, from the start.

Putting an MD SB at/near the beginning of the device breaks this case
and GRUB 1 doesn't know how to deal with it.

Cheers
Tim

  reply	other threads:[~2008-01-29  4:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 17:22 [PATCH] Use new sb type Jan Engelhardt
2008-01-28 18:19 ` David Greaves
2008-01-28 18:47   ` Peter Rabbitson
2008-01-28 19:32     ` David Greaves
2008-01-29  4:09       ` Tim Southerwood [this message]
2008-01-29  9:37         ` Peter Rabbitson
2008-01-29 11:25           ` Yes, but please provide the clue (was Re: [PATCH] Use new sb type) Moshe Yudkowsky
2008-01-28 19:10   ` [PATCH] Use new sb type Jan Engelhardt
2008-01-29 23:08   ` Bill Davidsen
2008-01-30 12:53     ` David Greaves
2008-02-08  0:23     ` Jan Engelhardt
2008-02-10 10:34       ` David Greaves
2008-02-10 12:12         ` Jan Engelhardt
2008-02-10 12:27           ` David Greaves
2008-02-10 12:30             ` Jan Engelhardt
2008-02-11  3:32               ` Bill Davidsen
2008-02-11  8:21               ` David Greaves
2008-02-11 18:28                 ` Bill Davidsen

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=479EA6DE.9070503@dionic.net \
    --to=ts@dionic.net \
    --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).