From: Nix <nix@esperi.org.uk>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: Wols Lists <antlists@youngman.org.uk>,
Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: New setup: partitions or raw devices
Date: Sat, 02 Dec 2017 20:35:39 +0000 [thread overview]
Message-ID: <87o9ngkgv8.fsf@esperi.org.uk> (raw)
In-Reply-To: <7b1c8f3c-08dd-771f-eab3-b75c11f3ea35@thelounge.net> (Reindl Harald's message of "Sat, 2 Dec 2017 15:01:13 +0100")
On 2 Dec 2017, Reindl Harald outgrape:
> Am 02.12.2017 um 14:19 schrieb Nix:
>> If RAID-5 and RAID-6 had no benefits at all over RAID-10 it is unlikely
>> they would still be in wide use. They are, even for new installations,
>> because they truly do offer benefits for some use cases. They may not
>> for yours, but that doesn't mean they don't for anyone
>
> yes, when you need far more than 8 TB...
I can't figure out whether you're castigating people who need more than
8TiB, castigating people who need less, applauding people who need more
than 8TiB, applauding people who need less, saying that people who need
more than 8TiB should use RAID 10, saying that people who need more
should use RAID 6, or *what*. All I can tell is that you want to be as
unpleasant as possible while saying it. (I suspect this ambiguity is
intentional, so that no matter what people assume you meant, you can
flame them for not interpreting it the other way.)
But then that's not surprising because you've morphed again to try to
escape from people's killfiles. Back you go into mine, *yet again*.
--
NULL && (void)
next prev parent reply other threads:[~2017-12-02 20:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 16:22 New setup: partitions or raw devices Gandalf Corvotempesta
2017-11-29 16:44 ` Reindl Harald
2017-11-29 16:52 ` Phil Turmel
2017-11-29 17:42 ` Gandalf Corvotempesta
2017-11-29 17:49 ` Phil Turmel
[not found] ` <CAJH6TXjFoUOCySnq2ErjTT9rb10XSc2saY=Q3RDheT7thOOFPg@mail.gmail.com>
[not found] ` <CAJH6TXhK5XgY-1v49oHcRXBugDMZ6QagKSa-deCA-Q7tPPLRyA@mail.gmail.com>
[not found] ` <CAJH6TXgbfgg_dk9oasVExn=RPVZqQDKN2AWAmPi1U2=PiACAHA@mail.gmail.com>
2017-11-29 19:54 ` Fwd: " Gandalf Corvotempesta
2017-11-29 22:10 ` Chris Murphy
2017-11-29 22:14 ` Gandalf Corvotempesta
2017-11-29 22:27 ` Chris Murphy
2017-11-29 22:14 ` Chris Murphy
2017-11-29 17:38 ` Gandalf Corvotempesta
2017-11-29 18:28 ` Reindl Harald
2017-11-29 19:51 ` Gandalf Corvotempesta
2017-11-29 20:02 ` Reindl Harald
2017-11-29 22:02 ` Gandalf Corvotempesta
2017-11-29 22:10 ` Reindl Harald
2017-11-29 22:25 ` Gandalf Corvotempesta
2017-11-29 22:34 ` Reindl Harald
2017-12-01 16:18 ` Nix
2017-12-02 13:01 ` Gandalf Corvotempesta
2017-11-29 22:20 ` Wol's lists
2017-11-29 22:27 ` Reindl Harald
2017-12-01 16:19 ` Nix
2017-12-01 16:27 ` Reindl Harald
2017-12-01 17:18 ` Wols Lists
2017-12-01 22:22 ` Nix
2017-12-01 23:44 ` Reindl Harald
2017-12-02 13:14 ` Gandalf Corvotempesta
2017-12-02 13:56 ` Reindl Harald
2017-12-02 17:12 ` Phil Turmel
2017-12-02 18:39 ` Reindl Harald
2017-12-02 13:19 ` Nix
2017-12-02 14:01 ` Reindl Harald
2017-12-02 20:35 ` Nix [this message]
2017-12-02 21:41 ` Reindl Harald
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=87o9ngkgv8.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--cc=gandalf.corvotempesta@gmail.com \
--cc=h.reindl@thelounge.net \
--cc=linux-raid@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