From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Bart Noordervliet <bart@noordervliet.net>
Cc: Hugo Mills <hugo-lkml@carfax.org.uk>, Chris Ball <cjb@laptop.org>,
linux-btrfs@vger.kernel.org
Subject: Re: Update to Project_ideas wiki page
Date: Wed, 17 Nov 2010 17:56:57 +0000 [thread overview]
Message-ID: <20101117175657.GB2401@selene> (raw)
In-Reply-To: <AANLkTi=YcVE44g9waRBHQPido4_xf1o5hE4zmTPqVBxN@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2336 bytes --]
On Wed, Nov 17, 2010 at 04:12:29PM +0100, Bart Noordervliet wrote:
> Can I suggest we combine this new RAID level management with a
> modernisation of the terminology for storage redundancy, as has been
> discussed previously in the "Raid1 with 3 drives" thread of March this
> year? I.e. abandon the burdened raid* terminology in favour of
> something that makes more sense for a filesystem.
Well, our current RAID modes are:
* 1 Copy ("SINGLE")
* 2 Copies ("DUP")
* 2 Copies, different spindles ("RAID1")
* 1 Copy, 2 Stripes ("RAID0")
* 2 Copies, 2 Stripes [each] ("RAID10")
The forthcoming RAID5/6 code will expand on that, with
* 1 Copy, n Stripes + 1 Parity ("RAID5")
* 1 Copy, n Stripes + 2 Parity ("RAID6")
(I'm not certain how "n" will be selected -- it could be a config
option, or simply selected on the basis of the number of
spindles/devices currently in the FS).
We could further postulate a RAID50/RAID60 mode, which would be
* 2 Copies, n Stripes + 1 Parity
* 2 Copies, n Stripes + 2 Parity
For brevity, we could collapse these names down to: 1C, 2C, 2CR,
1C2S, 2C2S, 1CnS1P, 1CnS2P, 2CnS1P, 2CnS2P. However, that's probably a
bit too condensed for useful readability. I'd support some set of
terms based on this taxonomy, though, as it's fairly extensible, and
tells you the details of the duplication strategy in question.
> Mostly this would involve a discussion about what terms would make
> most sense, though some changes in the behaviour of btrfs redundancy
> modes may be warranted if they make things more intuitive.
Consider the above a first suggestion. :)
> I could help you make these changes in your patches, or write my own
> patches against yours, though I'm also completely new to kernel
> development.
Probably best to keep the kernel internals unchanged for this
particular issue, as they don't make much difference to the naming,
but patches to the userspace side of things (mkfs.btrfs and btrfs fi
df specifically) should be fairly straightforward.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- <gdb> The enemy have elected for Death by Powerpoint. That's ---
what they shall get.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2010-11-17 17:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 3:19 Update to Project_ideas wiki page Chris Ball
2010-11-17 14:31 ` Hugo Mills
2010-11-17 15:12 ` Bart Noordervliet
2010-11-17 17:19 ` Xavier Nicollet
2010-11-17 17:52 ` Mike Fedyk
2010-11-17 17:56 ` Hugo Mills [this message]
2010-11-17 18:07 ` Gordan Bobic
2010-11-17 18:41 ` Bart Kus
2010-11-18 8:36 ` Gordan Bobic
2010-11-18 14:31 ` Bart Noordervliet
2010-11-18 15:02 ` Justin Ossevoort
2010-11-18 15:06 ` Gordan Bobic
2010-11-17 18:14 ` Andreas Philipp
2010-11-17 18:34 ` Hugo Mills
2010-11-26 14:57 ` Paul Komkoff
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=20101117175657.GB2401@selene \
--to=hugo-lkml@carfax.org.uk \
--cc=bart@noordervliet.net \
--cc=cjb@laptop.org \
--cc=linux-btrfs@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).