All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Reindl Harald <h.reindl@thelounge.net>,
	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 22:22:00 +0000	[thread overview]
Message-ID: <878temxf5j.fsf@esperi.org.uk> (raw)
In-Reply-To: <5A218EDB.6030909@youngman.org.uk> (Wols Lists's message of "Fri, 1 Dec 2017 17:18:19 +0000")

On 1 Dec 2017, Wols Lists stated:
> Yes it does have advantages, and yes I plan to put a raid-10 array on my
> new system, but if reducing wear or protecting data are your priorities,
> raid-10 is the wrong choice.

It depends on the access patterns. It's no worse at safeguarding data
than RAID-5 and can be better (some, but not all, combinations of
multiple disk failures will lead to no data loss, something which would
otherwise require RAID-6). It's faster at reads and much faster at
random writes. The cost: possibly quite a lot more spinning rust for the
amount of available storage. (For me, power-consumption considerations
led me to stick with RAID, though I've gone to RAID-6.)

-- 
NULL && (void)

  reply	other threads:[~2017-12-01 22:22 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 [this message]
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=878temxf5j.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.