From: John Robinson <john.robinson@anonymous.org.uk>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: nonstandard raid(4-ish) scheme
Date: Tue, 24 Jan 2012 12:51:19 +0000 [thread overview]
Message-ID: <4F1EA947.2080207@anonymous.org.uk> (raw)
In-Reply-To: <20120124030015.GQ11921@wantstofly.org>
On 24/01/2012 03:00, Lennert Buytenhek wrote:
> (I'm not on the list, please CC on replies.)
>
> Hi!
>
> While recently setting up a media server for a HTPC, I was wondering
> whether it'd be possible to set things up so that most disks can be
> kept spun down most of the time.
>
> Since the majority of the I/O on this sort of server is reads, the
> first idea was to store (directories of) media files entirely on
> individual disks, i.e. to not distribute them over all disks by
> striping, as that would require spinning up each disk on reads. So,
> creating a large RAID(5/6) array out of all of the disks wouldn't be
> option here.
>
> RAID1ing pairs of disks would work, but this is somewhat wasteful,
> as it eats up half of your space.
>
> The ideal way of doing this would be to take N-1 disks out of your N
> disk set, and create separate filesystems on each of the disks, and
> store different sets of files on them, while using the last disk,
> disk N, as a parity disk of the N-1 data disks.
>
> This is equivalent to raid4 with the stripe size equal the size of
> one disk, and where the data disks get individual /dev/mdX entries
> instead of being concatenated into one large /dev/mdX.
>
> Would this be easy to implement?
I think it already has been, as UnRAID:
http://en.wikipedia.org/wiki/Non-standard_RAID_levels#UnRAID
Cheers,
John.
next prev parent reply other threads:[~2012-01-24 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 3:00 nonstandard raid(4-ish) scheme Lennert Buytenhek
2012-01-24 12:51 ` John Robinson [this message]
2012-01-24 16:22 ` Christoph Hellwig
2012-01-24 20:51 ` David Brown
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=4F1EA947.2080207@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=buytenh@wantstofly.org \
--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).