From: Goswin von Brederlow <goswin-v-b@web.de>
To: NeilBrown <neilb@suse.de>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
Daniel Reurich <daniel@centurion.net.nz>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: md extension to support booting from raid whole disks.
Date: Sat, 09 May 2009 00:29:12 +0200 [thread overview]
Message-ID: <87ws8r2pqf.fsf@frosties.localdomain> (raw)
In-Reply-To: <21cdc7a16fbdd42979d52331db97c737.squirrel@neil.brown.name> (NeilBrown's message of "Sat, 9 May 2009 08:16:27 +1000 (EST)")
"NeilBrown" <neilb@suse.de> writes:
> On Sat, May 9, 2009 7:50 am, Goswin von Brederlow wrote:
>
>>>> So I still plan to offer a "--reserve-space=2M" option for mdadm to
>>>> allow the first 2M of each device to not used for raid data. Whether
>>>> any particular usage of this option is viable or not, is a different
>>>> question altogether.
>>
>> How exactly would that layout be then?
>>
>> Block 0 bootblock
>> Block 1 raid metadata
>> Block x 2M reserved space
>> Block x+2M start of raid data
>>
>> Like this?
>
> When using 1.2 metadata, yes, possible with bitmap
> inserted between the reserved space and the start of raid data.
That realy seems to be the best option. Simple to implement, simple to
use and if mdadm copies the reserved space from old to new drives when
adding one it gives us exactly what we want.
Are you working on that already or do you think it needs more discussion?
> When using 1.0, it would be
>
> Block 0..N-1 boot block and second stage
> Block N..near-the-end raid data
> Block x..y bitmap
> block z superblock
I never liked the idea of 1.0.
What actualy does happen when you have raid on partitions and resize a
partition? Am I right that the raid then can't be assembled until the
raid itself gets grown (and the superblock gets moved to the new end)?
> NeilBrown
next prev parent reply other threads:[~2009-05-08 22:29 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 12:08 md extension to support booting from raid whole disks Daniel Reurich
2009-04-27 15:08 ` Goswin von Brederlow
2009-04-28 4:58 ` H. Peter Anvin
2009-04-28 6:26 ` Luca Berra
2009-04-28 9:35 ` Goswin von Brederlow
2009-04-28 11:21 ` Daniel Reurich
2009-04-28 17:36 ` H. Peter Anvin
2009-04-28 22:23 ` Daniel Reurich
2009-04-28 23:30 ` H. Peter Anvin
2009-04-29 0:02 ` Daniel Reurich
2009-04-29 11:32 ` John Robinson
2009-04-28 18:24 ` Dan Williams
2009-04-28 22:19 ` Daniel Reurich
2009-04-28 22:26 ` Dan Williams
2009-05-01 21:04 ` Goswin von Brederlow
2009-05-01 21:24 ` Dan Williams
2009-05-01 22:33 ` Goswin von Brederlow
2009-05-02 12:07 ` John Robinson
2009-05-04 17:02 ` Goswin von Brederlow
2009-05-05 9:31 ` Michal Soltys
2009-04-28 23:05 ` Neil Brown
2009-04-28 23:20 ` H. Peter Anvin
2009-04-29 0:00 ` Daniel Reurich
2009-04-29 0:04 ` H. Peter Anvin
2009-04-29 0:20 ` Daniel Reurich
2009-04-29 0:28 ` H. Peter Anvin
2009-04-29 0:43 ` Daniel Reurich
2009-04-29 6:43 ` Gabor Gombas
2009-05-01 21:10 ` Goswin von Brederlow
2009-05-01 22:36 ` Rudy Zijlstra
2009-05-02 1:04 ` Daniel Reurich
2009-05-02 17:02 ` Michał Przyłuski
2009-05-03 1:33 ` Leslie Rhorer
2009-05-03 4:25 ` NeilBrown
2009-05-03 18:05 ` Leslie Rhorer
2009-05-04 3:04 ` Daniel Reurich
2009-05-08 21:50 ` Goswin von Brederlow
2009-05-08 22:16 ` NeilBrown
2009-05-08 22:29 ` Goswin von Brederlow [this message]
2009-05-12 5:39 ` Neil Brown
2009-05-12 19:44 ` Daniel Reurich
2009-05-13 11:12 ` Neil Brown
2009-05-14 2:21 ` Daniel Reurich
2009-05-15 16:13 ` H. Peter Anvin
2009-05-13 12:15 ` Bill Davidsen
2009-05-08 22:06 ` Goswin von Brederlow
2009-05-09 7:20 ` Peter Rabbitson
2009-05-10 1:29 ` Goswin von Brederlow
[not found] ` <87presxwu4.fsf@frosties.localdomain>
[not found] ` <1241219902.9516.6.camel@poledra.romunt.nl>
[not found] ` <87bpq8n6ym.fsf@frosties.localdomain>
2009-05-04 20:57 ` Rudy Zijlstra
2009-05-04 22:33 ` Daniel Reurich
2009-05-05 0:26 ` John Robinson
2009-05-05 9:03 ` Keld Jørn Simonsen
2009-05-08 21:18 ` Goswin von Brederlow
2009-04-29 22:43 ` md extension to support booting from raid whole disks, raid6, grub2, lvm2 Michael Ole Olsen
2009-05-01 21:36 ` Goswin von Brederlow
2009-04-29 7:45 ` md extension to support booting from raid whole disks Luca Berra
2009-04-29 16:55 ` H. Peter Anvin
2009-04-29 20:38 ` Luca Berra
2009-04-30 6:59 ` Gabor Gombas
2009-04-30 8:11 ` Luca Berra
2009-04-30 13:01 ` John Robinson
2009-04-28 23:41 ` Daniel Reurich
2009-04-29 0:01 ` H. Peter Anvin
2009-05-01 21:33 ` Goswin von Brederlow
2009-04-28 7:08 ` Daniel Reurich
2009-04-28 23:07 ` Neil Brown
2009-04-28 23:21 ` Daniel Reurich
2009-04-28 23:37 ` H. Peter Anvin
2009-04-29 0:05 ` Daniel Reurich
2009-04-29 0:06 ` H. Peter Anvin
2009-04-29 0:36 ` Daniel Reurich
2009-04-29 0:44 ` H. Peter Anvin
[not found] ` <1240968482.18303.1028.camel@ezra>
[not found] ` <49F7B162.8060301@zytor.com>
2009-04-29 2:08 ` Daniel Reurich
2009-04-29 2:33 ` H. Peter Anvin
2009-04-30 2:41 ` Daniel Reurich
2009-04-29 7:07 ` Gabor Gombas
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=87ws8r2pqf.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=daniel@centurion.net.nz \
--cc=linux-raid@vger.kernel.org \
--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).