From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: linux-raid@vger.kernel.org
Subject: Re: Roadmap for md/raid ???
Date: Mon, 19 Jan 2009 19:41:46 +0100 [thread overview]
Message-ID: <20090119184146.GA4419@lazy.lzy> (raw)
In-Reply-To: <4974C5DA.3090806@rabbit.us>
Hi,
> Or alternatively you use LVM from the start. Then you only need to
> "cleverly partition" the new drives, use the first partition in the old
> RAID, use the second partition for a new smaller raid, join the new raid
> to the VG of the old raid and voilla - no wasted space.
I think that's exactly what I'm doing right now
with my test array.
Basically I've 7 disks, all, but two, different
in size.
I created partitions, of equal size between disks,
than I configured 4 RAID-6 devices (with 7, 6, 5, 4
partitions respectively) and put everything together
with LVM.
This works fine, it is possible to add HDs, or change
the old ones with bigger new ones.
One issue is that, with time, the larger HDs will
have many partitions, this led to use GPT table
(max 128 partitions) instead of DOS.
Metadata needs to be 1.x, of course.
The second point is the "annoyance" of creating
those partitions on the new HDs and adding them
to the proper md devices.
Of course, nothing particularly difficult, nevertheless
it would be nice to have everything integrated into
the md driver and transparent to the user.
Just an idea of improvement, nothing more.
Side note: if anybody has suggestions on how to script
the complete procedure of adding/replacing an HD in
such configuration, I'll appreciate it a lot!
Thanks,
bye,
--
piergiorgio
next prev parent reply other threads:[~2009-01-19 18:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 4:10 Roadmap for md/raid ??? Neil Brown
2008-12-19 15:44 ` Chris Worley
2008-12-19 15:51 ` Justin Piszcz
2008-12-19 16:13 ` Bernd Schubert
2008-12-30 18:12 ` Janek Kozicki
2008-12-30 18:15 ` Janek Kozicki
2009-01-19 0:54 ` Neil Brown
2009-01-19 12:25 ` Keld Jørn Simonsen
2009-01-19 19:03 ` thomas62186218
2009-01-19 20:00 ` Jon Nelson
2009-01-19 20:18 ` Greg Freemyer
2009-01-19 20:30 ` Jon Nelson
2009-01-11 18:14 ` Piergiorgio Sartor
2009-01-19 1:40 ` Neil Brown
2009-01-19 18:19 ` Piergiorgio Sartor
2009-01-19 18:26 ` Peter Rabbitson
2009-01-19 18:41 ` Piergiorgio Sartor [this message]
2009-01-19 21:08 ` Keld Jørn Simonsen
2009-01-14 20:43 ` Bill Davidsen
2009-01-19 2:05 ` Neil Brown
[not found] ` <49740C81.2030502@tmr.com>
2009-01-19 22:32 ` Neil Brown
2009-01-21 17:04 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2008-12-19 9:01 Aw: " piergiorgio.sartor
2008-12-19 17:01 ` Dan Williams
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=20090119184146.GA4419@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--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).