linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Charles Zeitler <cfzeitler@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: raid levels and NAS drives
Date: Mon, 10 Oct 2016 08:07:53 -0400	[thread overview]
Message-ID: <c7e8a508-1e55-4049-1e9e-63942f80d030@gmail.com> (raw)
In-Reply-To: <CAB9fVVH6S-Y0Li=6xyw2P23CEPwVRA6hRbjJNi+_3etHnqMh1w@mail.gmail.com>

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?
Before I answer the question, it is worth explaining the differences 
between the marketing terms 'desktop', 'enterprise', 'NAS', and 'video' 
as they relate to hard drives.

The big distinguishing factors that make a hard drive a 'desktop' drive 
are that it will retry reading a bad sector for an insanely long time 
(multiple minutes on most drives), it usually won't run at more than 
7200 RPM, and it may have better energy efficiency and be designed to 
handle more load/unload cycles for the heads (that is, it's designed for 
regular desktop/laptop usage patterns).

An 'enterprise' drive by contrast has support for setting the read 
timeout and write timeout on bad sectors (variously called TLER, SCT 
ERC, and numerous other things), typically runs at higher speeds (10k or 
15k RPM), and is usually designed for continuous 24/7 operation.

A 'NAS' drive is somewhere between a 'desktop' and an 'enterprise' 
drive, they have TLER/ERC, but usually don't run at more than 7200 RPM, 
and are usually designed with energy efficiency in mind.

A 'video' or 'security' drive is a special case that's only marketed by 
WD as far as I know, they're designed for low error rate, 24/7 
operation, and very high performance streaming writes and reads.

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).

  parent reply	other threads:[~2016-10-10 12:08 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 [this message]
2016-10-11 22:10   ` Nicholas D Steeves
2016-10-12 11:25     ` Austin S. Hemmelgarn

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=c7e8a508-1e55-4049-1e9e-63942f80d030@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=cfzeitler@gmail.com \
    --cc=linux-btrfs@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).