linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: David T-G <davidtg-robot@justpickone.org>,
	Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: disks & prices plus python
Date: Thu, 21 May 2020 14:42:14 +0100	[thread overview]
Message-ID: <5EC68536.4040000@youngman.org.uk> (raw)
In-Reply-To: <20200521131751.GQ1415@justpickone.org>

On 21/05/20 14:17, David T-G wrote:
> % So if you really want to use them in a raid array, I'd go for a 6TB
> % raid-10. Okay, you've lost 3TB of disk space, but you've bought a
> % 66% chance of surviving a 2-disk failure.
> 
> Heh.  Except that this box has only three ports, so one was going to
> become USB storage or some such anyway.  But that means I can't have a
> RAID10 vol ...

Three SATA ports? That sounds very stingy! (Or is it four, but one's the
DVD?)

This is what I've bought for my new PC
https://www.amazon.co.uk/StarTech-com-Port-Express-eSATA-Controller-Silver-Black/dp/B00952N2DQ/ref=pd_ybh_a_47?_encoding=UTF8&psc=1&refRID=2B248DH9763DDGHGN5A6

An expensive gaming mobo, with 6 SATA ports, but if I want NVMe, or a
second graphics card, or whatever whatever, some of the lanes get taken
away. And of course I do want a 2nd graphics card (this machine is
destined to be double-headed, when I can get it to work :-)

And then for my old system, I'm planning to buy
https://www.amazon.co.uk/gp/product/B07T8XNQT6/ref=ox_sc_saved_title_2?smid=A32IGEZ3DX93HZ&psc=1

or something similar. That machine has 5 SATA ports (or only 4 if
PATA-mode is enabled), and I'm planning to stick a bunch of 500GB or 1TB
drives in it for playing with. So especially if I split the 1TB drives
into 500GB partitions, that's some humungous raids for testing with :-)

Cheers,
Wol

  reply	other threads:[~2020-05-21 13:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 20:05 failed disks, mapper, and "Invalid argument" David T-G
2020-05-20 23:23 ` Wols Lists
2020-05-20 23:53   ` David T-G
2020-05-21  8:09     ` Wols Lists
2020-05-21 11:01       ` David T-G
2020-05-21 11:55         ` Wols Lists
2020-05-21 12:30           ` disks & prices plus python (was "Re: failed disks, mapper, and "Invalid argument"") David T-G
2020-05-21 13:07             ` antlists
2020-05-21 13:17               ` disks & prices plus python David T-G
2020-05-21 13:42                 ` Wols Lists [this message]
2020-05-21 13:46                   ` David T-G
2020-05-21 11:01       ` failed disks, mapper, and "Invalid argument" David T-G
2020-05-21 11:24         ` David T-G
2020-05-21 12:00           ` Wols Lists
2020-05-21 12:33             ` re-add syntax (was "Re: failed disks, mapper, and "Invalid argument"") David T-G
2020-05-21 13:01               ` antlists
2020-05-21 13:15                 ` re-add syntax David T-G
2020-05-21 18:07                   ` David T-G
2020-05-21 18:40                     ` Roger Heflin
2020-05-21 22:52                       ` David T-G
2020-05-21 23:17                         ` antlists
2020-05-21 23:53                           ` David T-G
2020-05-21  8:13     ` failed disks, mapper, and "Invalid argument" Wols Lists
2020-05-21 11:04       ` David T-G

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=5EC68536.4040000@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=davidtg-robot@justpickone.org \
    --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;
as well as URLs for NNTP newsgroup(s).