From: Goswin von Brederlow <goswin-v-b@web.de>
To: Peter Rabbitson <rabbit+list@rabbit.us>
Cc: Micha Przyuski <mikylie@gmail.com>,
Daniel Reurich <daniel@centurion.net.nz>,
linux-raid@vger.kernel.org, neilb@suse.de
Subject: Re: md extension to support booting from raid whole disks.
Date: Sun, 10 May 2009 03:29:34 +0200 [thread overview]
Message-ID: <8763g9ycch.fsf@frosties.localdomain> (raw)
In-Reply-To: <4A052EBE.5010605@rabbit.us> (Peter Rabbitson's message of "Sat, 09 May 2009 09:20:30 +0200")
Peter Rabbitson <rabbit+list@rabbit.us> writes:
> Goswin von Brederlow wrote:
>> If the hidden raid1 is just reserved space that is considered part of
>> the raid metadata then this moves completly into mdadm userspace. The
>> extra complexity comes down to "read reserved space from old disk,
>> write reserved space to new disk". In the most basic form that is 3
>> lines of code (declare buffer, read, write).
>>
>
> This is the best description of the problem/benefit so far. Also when
> deciding on the size of the reserved space, factor in possible
> bitmap size explosion when moving from say a 4x300G raid6 to a 4x2T raid6.
>
> +1 on this feature request
>
> Cheers
From what Neil described it should be no problem to resize the amount
of space used for metadata. It would have to copy around all the data
of the raid, do a reshape basically, but that isn't hard. Or it could
be limited to adding drives, which would need to do a resync anyway,
e.g. something like
mdadm --add --reserved-space=3M --bitmap-space=4M /dev/md0 /dev/sdx
MfG
Goswin
PS: tests seem to show though that smaller bitmaps are faster
next prev parent reply other threads:[~2009-05-10 1: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
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 [this message]
[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=8763g9ycch.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=daniel@centurion.net.nz \
--cc=linux-raid@vger.kernel.org \
--cc=mikylie@gmail.com \
--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.