From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] improve documentation of snapshot unaware defrag
Date: Mon, 28 Dec 2015 03:07:55 +0100 [thread overview]
Message-ID: <1451268475.6320.39.camel@scientia.net> (raw)
In-Reply-To: <20151228015807.GM1586@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Mon, 2015-12-28 at 01:58 +0000, Hugo Mills wrote:
> Isn't this an FAQ already? There is already a patch to rename the
> RAID modes. It's been sitting in the progs patch queue for about 2
> years, because none of the senior devs has acked it yet (since it's a
> big user-visible change).
Uhm... yeah, it's a bit invasive... but that happens when such improper
naming is done in the first place :-/
It's similar to when tools wrongly or ambiguously use SI prefixes,
instead of proper kB, MB, GB, etc. (for base 1000) respectively KiB,
MiB, GiB, etc. (for base 1024).
Especially just using K,M,G, is simply evil and should lead to public
punishment ;-)
I'm also not really fond of what btrfs took over from LVM,
namely kKmMgGtTpPeE,... it's ambiguous or at least unclean as well...
Best would be probably if we don't use "raid" as names at all (or just
as aliases for the actual canonical names), but rather describe what's
actually...
E.g.
classic RAID1 = mirror
btrfs RAID1 = dup2 or something similar like clone2, replica2
classic RAID0 = striped
RAID5/6 = parityN
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-12-28 2:07 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 [this message]
2015-12-28 9:12 ` Duncan
2015-12-28 2:51 ` Duncan
2015-12-28 3:03 ` Christoph Anton Mitterer
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=1451268475.6320.39.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=1i5t5.duncan@cox.net \
--cc=hugo@carfax.org.uk \
--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).