From: Phillip Susi <psusi@ubuntu.com>
To: ashford@whisperpc.com
Cc: Jose Manuel Perez Bethencourt <jmperezbeth@gmail.com>,
Chris Murphy <lists@colorremedies.com>,
"sys.syphus" <syssyphus@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: I need to P. are we almost there yet?
Date: Wed, 31 Dec 2014 18:38:56 -0500 [thread overview]
Message-ID: <54A48910.60701@ubuntu.com> (raw)
In-Reply-To: <1da0cf9a75a357c960af323aa56c7530.squirrel@webmail.wanet.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/31/2014 12:27 PM, ashford@whisperpc.com wrote:
> I see this as a CRITICAL design flaw. The reason for calling it
> CRITICAL is that System Administrators have been trained for >20
> years that RAID-10 can usually handle a dual-disk failure, but the
> BTRFS implementation has effectively ZERO chance of doing so.
Sure, but you never *count* on that second failure since it is a (
relatively even ) probability game.
> In order to remove this potentially catestrophic confusion, BTRFS
> should either call their "RAID-10" implementation something else,
> or they should adhere to the long-established definition of
> RAID-10.
Personally I'd prefer it follow the way mdadm does it, which is much
better than what the rest of the industry calls raid-10, which is to
say, simply a naive raid-0 on top of raid-1. I'm very happy with my 3
disk offset layout raid-10 which gets the sequential read throughput
of a 3 disk raid-0, while still being able to handle a single drive
failure.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJUpIkQAAoJENRVrw2cjl5R/wAIAKNU0NfEFGXLQK0lB1kZMJQt
WrBjKih8xG2WIYAqYCHoNTWJtmCZOCHtltt+OsUb8Pa8u075ALtEQBRNminLLuqV
LjREOyOzvzaDfNSEhptdBZ4YazqFt6UChWtu7RWhMtb7u61pmqMJatDhxLe+2CF9
YQE3qgLfP+PAMIGO/xN5m+hYba4hbF/MoqQ/XN7Z1VWvT9FNR7Dn8frflpmI2Cyh
iAravNS78hUjbxTtNz1qVXLosDVsjyZpz9UY9occNJ/vlF/GMd5q2c8xXkDTczGB
O9B55OXGzfmzPZzlNJ2MyBLgwQx/huPH8RiyuuIdy3AVubc/pXuAZQqaydf/lQg=
=qwW+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-31 23:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 18:56 I need to P. are we almost there yet? sys.syphus
2014-12-29 19:00 ` sys.syphus
2014-12-29 19:04 ` Hugo Mills
2014-12-29 20:25 ` sys.syphus
2014-12-29 21:50 ` Hugo Mills
2014-12-29 21:16 ` Chris Murphy
2014-12-30 0:20 ` ashford
[not found] ` <CALBWd85UsSih24RhwpmDeMjuMWCKj9dGeuZes5POj6qEFkiz2w@mail.gmail.com>
2014-12-30 17:09 ` Fwd: " Jose Manuel Perez Bethencourt
2014-12-30 21:44 ` Phillip Susi
2014-12-30 23:17 ` ashford
2014-12-31 2:45 ` Phillip Susi
2014-12-31 17:27 ` ashford
2014-12-31 23:38 ` Phillip Susi [this message]
2015-01-01 1:26 ` Chris Samuel
2015-01-01 20:12 ` Roger Binns
2015-01-02 3:47 ` Duncan
2015-01-02 13:42 ` Austin S Hemmelgarn
2015-01-02 17:45 ` Brendan Hide
2015-01-02 19:41 ` Austin S Hemmelgarn
2014-12-29 21:13 ` Chris Murphy
2015-01-03 11:34 ` Bob Marley
2015-01-03 13:11 ` Duncan
2015-01-03 18:53 ` Bob Marley
2015-01-03 19:03 ` sys.syphus
2015-01-03 18:55 ` sys.syphus
2015-01-04 3:22 ` Duncan
2015-01-04 3:54 ` Hugo Mills
2015-01-03 21:58 ` Roman Mamedov
2015-01-04 3:24 ` 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=54A48910.60701@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=ashford@whisperpc.com \
--cc=jmperezbeth@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=syssyphus@gmail.com \
/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).