Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
	Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: New setup: partitions or raw devices
Date: Fri, 01 Dec 2017 16:18:32 +0000	[thread overview]
Message-ID: <87y3mmzajr.fsf@esperi.org.uk> (raw)
In-Reply-To: <46648c36-3a63-1524-995d-786620dc716e@thelounge.net> (Reindl Harald's message of "Wed, 29 Nov 2017 23:34:17 +0100")

On 29 Nov 2017, Reindl Harald said:

> Am 29.11.2017 um 23:25 schrieb Gandalf Corvotempesta:
>> Look at one of Intel DC SSD, the S3610 1.6TB is about 1500 USD. Twice
>> the price, 40% less capacity
>
> and do you really need them?
> for what usecase?

Not bricking or corrupting themselves when the power goes out.

Intel DC SSDs are the only SSDs I have *ever* heard of surviving such
tests.

(btw, if you really are overprovisioning SSDS by hand, 2--5% is not
remotely enough. 10% is not really enough. I'd go for 15--20%.

-- 
NULL && (void)

  reply	other threads:[~2017-12-01 16:18 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 [this message]
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
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=87y3mmzajr.fsf@esperi.org.uk \
    --to=nix@esperi.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