From: Bill Davidsen <davidsen@tmr.com>
To: James Lee <james.lee@cantab.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Proposal: non-striping RAID4
Date: Wed, 14 Nov 2007 18:16:14 -0500 [thread overview]
Message-ID: <473B81BE.8070309@tmr.com> (raw)
In-Reply-To: <ef2613f30711131706g31b7b7adm61add82fef3ff94a@mail.gmail.com>
James Lee wrote:
> >From a quick search through this mailing list, it looks like I can
> answer my own question regarding RAID1 --> RAID5 conversion. Instead
> of creating a RAID1 array for the partitions on the two biggest
> drives, it should just create a 2-drive RAID5 (which is identical, but
> can be expanded as with any other RAID5 array).
>
> So it looks like this should work I guess.
I believe what you want to create might be a three drive raid-5 with one
failed drive. That way you can just add a drive when you want.
mdadm -C -c32 -l5 -n3 -amd /dev/md7 /dev/loop[12] missing
Then you can add another drive:
mdadm --add /dev/md7 /dev/loop3
The output are at the end of this message.
But in general think it would be really great to be able to have a
format which would do raid-5 or raid-6 over all the available parts of
multiple drives, and since there's some similar logic for raid-10 over a
selection of drives it is clearly possible. But in terms of the benefit
to be gained, unless it fails out of the code and someone feels the
desire to do it, I can't see much joy to ever having such a thing.
The feature I would really like to have is raid5e, distributed spare so
head motion is spread over all drives. Don't have time to look at that
one, either, but it really helps performance under load with small arrays.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-11-14 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 0:57 Proposal: non-striping RAID4 James Lee
2007-11-12 1:29 ` Bill Davidsen
2007-11-13 23:48 ` James Lee
2007-11-14 1:06 ` James Lee
2007-11-14 23:16 ` Bill Davidsen [this message]
2007-11-15 0:24 ` James Lee
2007-11-15 6:01 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2007-11-23 15:58 Chris Green
2008-05-22 21:15 Tony Germano
2008-05-22 22:10 ` David Lethe
2008-05-22 22:56 ` Tony Germano
2008-05-23 15:12 ` Roger Heflin
2008-05-23 15:47 ` Chris Green
2008-05-24 14:21 ` Bill Davidsen
2008-05-24 14:19 ` Chris Green
2008-05-28 23:14 ` Bill Davidsen
2008-05-30 17:23 ` Tony Germano
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=473B81BE.8070309@tmr.com \
--to=davidsen@tmr.com \
--cc=james.lee@cantab.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 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.