Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
To: Nix <nix@esperi.org.uk>, Reindl Harald <h.reindl@thelounge.net>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: New setup: partitions or raw devices
Date: Sat, 2 Dec 2017 14:01:56 +0100	[thread overview]
Message-ID: <de890073-cfa0-ed99-15aa-da7bb5dd5170@gmail.com> (raw)
In-Reply-To: <87y3mmzajr.fsf@esperi.org.uk>

Il 01/12/2017 17:18, Nix ha scritto:
>
> 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.

Exactly.
And additionally, enterprise SSDs are far more reliable than consumer SSDs,
in a RAID-1, where both disks will get the same identical write pattern, 
the risk
for a double failure at the same time is high.

And if you have to proactively replace an SSD before it fails,
then your are not using "inexpesive" disks anymore.

  reply	other threads:[~2017-12-02 13:01 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 [this message]
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=de890073-cfa0-ed99-15aa-da7bb5dd5170@gmail.com \
    --to=gandalf.corvotempesta@gmail.com \
    --cc=h.reindl@thelounge.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    /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