From: Ryan Wagoner <rswagoner@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: New raid level suggestion.
Date: Thu, 30 Dec 2010 09:24:32 -0500 [thread overview]
Message-ID: <AANLkTinJCQsaOuzQub9A7qU_HjGhUuXpp1oq+=5hTb3E@mail.gmail.com> (raw)
In-Reply-To: <20101230082356.GC2986@bitwizard.nl>
On Thu, Dec 30, 2010 at 3:23 AM, Rogier Wolff <R.E.Wolff@bitwizard.nl> wrote:
> So I was thinking.... He's resigned himself to a configuration where
> he pays for 4x the disk space and only gets 2x the available space.
>
> So he could run his array in RAID10 mode, however when a drive fails,
> a fallback to raid5 would be in order. In this case, after the resync
> a single-drive-failure tolerance is again obtained.
>
> In practise scaling down to raid5 is not easy/possible. RAID4 however
> should be doable.
>
> In fact this can almost be implemented entirely in userspace. Just
> remove the mirror drive from the underlying raid0, and reinitialize as
> raid4. If you do this correctly the data will still be there....
>
> Although doing this with an active filesystem running on these drives
> is probably impossible due to "device is in use" error messages....
Paying for 4x the disk space and only getting 2x is about performance.
You can't just view disks by the raw space they provide.
Even if the scenario of converting RAID10 to RAID4 was possible you
now have no redundancy during the conversion. The chance of a disk
failing is greater than just running the RAID10 until you can replace
the faulty disk. Not to mention the performance penalty of the resync
parity calculation. RAID10 when degraded has minor hit to performance
compared to a RAID level with parity.
All you need to do is purchase 5 disks if you want 4 in RAID10. Have
the cold spare ready when one fails. This reduces the replacement time
as you don't have to wait for a drive to be ordered.
Ryan
prev parent reply other threads:[~2010-12-30 14:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 8:23 New raid level suggestion Rogier Wolff
2010-12-30 8:47 ` Steven Haigh
2010-12-30 9:42 ` Rogier Wolff
2010-12-30 10:39 ` Stan Hoeppner
2010-12-30 11:58 ` John Robinson
2010-12-30 13:11 ` Stan Hoeppner
2010-12-30 18:10 ` John Robinson
2010-12-31 10:23 ` Stan Hoeppner
2010-12-30 23:20 ` Why won't mdadm start several RAIDs that appear to be fine? Jim Schatzman
2010-12-31 1:08 ` Neil Brown
2010-12-31 3:38 ` Why won't mdadm start several RAIDs that appear to be fine? Info from "mdadm -A --verbose" Jim Schatzman
2010-12-31 3:51 ` Why won't mdadm start several RAIDs that appear to be fine? SOLVED! Jim Schatzman
2011-01-03 4:33 ` New raid level suggestion Leslie Rhorer
2011-01-04 15:29 ` Rogier Wolff
2010-12-30 10:01 ` Neil Brown
2010-12-30 14:24 ` Ryan Wagoner [this message]
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='AANLkTinJCQsaOuzQub9A7qU_HjGhUuXpp1oq+=5hTb3E@mail.gmail.com' \
--to=rswagoner@gmail.com \
--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).