From: Brendan Hide <brendan@swiftspirit.co.za>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Cc: Russell Coker <russell@coker.com.au>
Subject: Re: Help with space
Date: Fri, 02 May 2014 11:28:13 +0200 [thread overview]
Message-ID: <5363652D.2080602@swiftspirit.co.za> (raw)
In-Reply-To: <pan$b29aa$ed2c5b17$e83ea42c$5e85b880@cox.net>
On 02/05/14 10:23, Duncan wrote:
> Russell Coker posted on Fri, 02 May 2014 11:48:07 +1000 as excerpted:
>
>> On Thu, 1 May 2014, Duncan <1i5t5.duncan@cox.net> wrote:
>> [snip]
>> http://www.eecs.berkeley.edu/Pubs/TechRpts/1987/CSD-87-391.pdf
>>
>> Whether a true RAID-1 means just 2 copies or N copies is a matter of
>> opinion. Papers such as the above seem to clearly imply that RAID-1 is
>> strictly 2 copies of data.
> Thanks for that link. =:^)
>
> My position would be that reflects the original, but not the modern,
> definition. The paper seems to describe as raid1 what would later come
> to be called raid1+0, which quickly morphed into raid10, leaving the
> raid1 description only covering pure mirror-raid.
Personally I'm flexible on using the terminology in day-to-day
operations and discussion due to the fact that the end-result is "close
enough". But ...
The definition of "RAID 1" is still only a mirror of two devices. As far
as I'm aware, Linux's mdraid is the only raid system in the world that
allows N-way mirroring while still referring to it as "RAID1". Due to
the way it handles data in chunks, and also due to its "rampant layering
violations", *technically* btrfs's "RAID-like" features are not "RAID".
To differentiate from "RAID", we're already using lowercase "raid" and,
in the long term, some of us are also looking to do away with "raid{x}"
terms altogether with what Hugo and I last termed as "csp notation".
Changing the terminology is important - but it is particularly non-urgent.
--
__________
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
next prev parent reply other threads:[~2014-05-02 9:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:19 Help with space Justin Brown
2014-02-27 19:27 ` Chris Murphy
2014-02-27 19:51 ` Chris Murphy
2014-02-27 20:49 ` otakujunction
2014-02-27 21:11 ` Chris Murphy
2014-02-28 0:12 ` Dave Chinner
2014-02-28 0:27 ` Chris Murphy
2014-02-28 4:21 ` Dave Chinner
2014-02-28 5:49 ` Chris Murphy
2014-02-28 4:34 ` Roman Mamedov
2014-02-28 7:27 ` Duncan
2014-02-28 7:37 ` Roman Mamedov
2014-02-28 7:46 ` Justin Brown
2014-05-01 1:52 ` Russell Coker
2014-05-01 5:33 ` Duncan
2014-05-02 1:48 ` Russell Coker
2014-05-02 8:23 ` Duncan
2014-05-02 9:28 ` Brendan Hide [this message]
2014-05-02 19:21 ` Chris Murphy
2014-05-02 21:08 ` Hugo Mills
2014-05-02 22:33 ` Chris Murphy
2014-05-03 16:31 ` Austin S Hemmelgarn
2014-05-03 19:09 ` Chris Murphy
2014-05-03 20:52 ` Austin S Hemmelgarn
2014-05-03 23:16 ` Chris Murphy
2014-02-28 6:13 ` Chris Murphy
2014-02-28 6:26 ` Chris Murphy
2014-02-28 7:39 ` Justin 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=5363652D.2080602@swiftspirit.co.za \
--to=brendan@swiftspirit.co.za \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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