linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Nicholas D Steeves <nsteeves@gmail.com>
Cc: Charles Zeitler <cfzeitler@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: raid levels and NAS drives
Date: Wed, 12 Oct 2016 07:25:00 -0400	[thread overview]
Message-ID: <5dd67e2b-49fe-6f45-ad31-f1a75fc7b80c@gmail.com> (raw)
In-Reply-To: <20161011221031.GB5515@DigitalMercury.dynalias.net>

On 2016-10-11 18:10, Nicholas D Steeves wrote:
> On Mon, Oct 10, 2016 at 08:07:53AM -0400, Austin S. Hemmelgarn wrote:
>> On 2016-10-09 19:12, Charles Zeitler wrote:
>>> Is there any advantage to using NAS drives
>>> under RAID levels,  as oppposed to regular
>>> 'desktop' drives for BTRFS?
> [...]
>> So, as for what you should use in a RAID array, here's my specific advice:
>> 1. Don't worry about enterprise drives unless you've already got a system
>> that has them.  They're insanely overpriced for relatively minimal benefit
>> when compared to NAS drives.
>> 2. If you can afford NAS drives, use them, they'll get you the best
>> combination of energy efficiency, performance, and error recovery.
>> 3. If you can't get NAS drives, most desktop drives work fine, but you will
>> want to bump up the scsi_command_timer attribute in the kernel for them (200
>> seconds is reasonable, just make sure you have good cables and a good
>> storage controller).
>> 4. Avoid WD Green drives, without special effort, they will get worse
>> performance and have shorter lifetimes than any other hard disk I've ever
>> seen.
>> 5. Generally avoid drives with a capacity over 1TB from manufacturers other
>> than WD, HGST, and Seagate, most of them are not particularly good quality
>> (especially if it's an odd non-power-of-two size like 5TB).
>
> +1 !  Additionally, is it still the case that it is generally safer to
> buy the largest capacity disks offered by the previous generation of
> technology rather than the current largest capacity?  eg: right now
> that would be 4TB or 6TB, and not 8TB or 10TB.
In general, yes, but you're normally safe as long as you're not using 
SMR disks.  I've used a couple of 8TB non-SMR drives, and they work 
perfectly fine (although they're insanely expensive), it's just been the 
SMR stuff that's been an issue (and you shouldn't be using them for 
non-archival storage anyway).

      reply	other threads:[~2016-10-12 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-09 23:12 raid levels and NAS drives Charles Zeitler
2016-10-10  0:01 ` Tomasz Kusmierz
     [not found]   ` <CAN05THSUtzUTXxKuQ7+fr7SDsbd0kGn8OGsXmkErS79Rh1ufLQ@mail.gmail.com>
2016-10-10  2:25     ` Tomasz Kusmierz
2016-10-10  7:26       ` Peter Becker
2016-10-10 12:07 ` Austin S. Hemmelgarn
2016-10-11 22:10   ` Nicholas D Steeves
2016-10-12 11:25     ` Austin S. Hemmelgarn [this message]

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=5dd67e2b-49fe-6f45-ad31-f1a75fc7b80c@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=cfzeitler@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nsteeves@gmail.com \
    /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).