From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] improve documentation of snapshot unaware defrag
Date: Mon, 28 Dec 2015 04:03:05 +0100 [thread overview]
Message-ID: <1451271785.6320.47.camel@scientia.net> (raw)
In-Reply-To: <pan$9c20a$2f693c09$f337c417$3719992c@cox.net>
[-- Attachment #1: Type: text/plain, Size: 2055 bytes --]
On Mon, 2015-12-28 at 02:51 +0000, Duncan wrote:
> 1) Btrfs very specifically and deliberately uses *lowercase* raidN
> in part to make that distinction, as the btrfs variants are chunk-
> level (and designed so that at some point in the future they can be
> subvolume and/or file level), not device-level (and at that future
> point, not necessarily filesystem level either).
I guess no "normal" user would expect or understand that lower/upper
case would imply any distinction.
> 2) Regarding btrfs raid1 and raid10's current very specific two-way-
> mirroring in particular, limiting to two-way-mirroring in the 3+
> devices
> case is well within established definitions and historic usage.
> Apparently, the N-devices = N-way-mirroring usage is relatively new,
> arguably first popularized by Linux mdraid, after which various
> hardware
> raid suppliers also implemented it due to competitive pressure. But
> only
> two-way-mirroring is required by the RAID-1 definition.
No, this is not true.
This http://www.eecs.berkeley.edu/Pubs/TechRpts/1987/CSD-87-391.pdf is
the original paper on RAID.
Chapter 7 describes RAID1 and the clearly says "all disks are
duplicated" as well as "Level 1 RAID has only one data disk".
I wouldn't know any single case of a HW RAID controller (and we've had
quite a few of them here at the Tier2) or other software implementation
where RAID1 had another meaning than "N disks, N mirrors".
> Even were that not the case, point #1, btrfs' very specific use of
> *lowercase* raid1, still covers the two-way-limitation case just as
> well
> as it covers the chunk-level case.
Hmm wouldn't still change anything, IMHO,... saying "lower case RAID is
something different than upper case RAID" would be just a bit ...
uhm... weird.
Actually, because btrfs doing it at the chunk level (while RAID being
at the device level), proves while my point that "raid" or "RAID" or
any other lower/upper case combination shouldn't be used at all.
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-12-28 3:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 1:26 defrag vs autodefrag Donald Pearson
2015-12-21 3:22 ` Duncan
2015-12-21 8:14 ` Hugo Mills
2015-12-21 9:28 ` Filipe Manana
2015-12-22 20:16 ` Christoph Anton Mitterer
2015-12-22 20:30 ` Hugo Mills
2015-12-23 2:16 ` Duncan
2015-12-27 3:03 ` [PATCH] improve documentation of snapshot unaware defrag Christoph Anton Mitterer
2015-12-27 3:10 ` Christoph Anton Mitterer
2015-12-27 7:09 ` Duncan
2015-12-28 0:50 ` Christoph Anton Mitterer
2015-12-28 1:58 ` Hugo Mills
2015-12-28 2:07 ` Christoph Anton Mitterer
2015-12-28 9:12 ` Duncan
2015-12-28 2:51 ` Duncan
2015-12-28 3:03 ` Christoph Anton Mitterer [this message]
2015-12-28 6:12 ` Duncan
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=1451271785.6320.47.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=1i5t5.duncan@cox.net \
--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).