All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Mikael Abrahamsson <swmike@swm.pp.se>,
	wiebittewas <wiebittewas@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: seagate-"archive"-disks with raid6?
Date: Sat, 13 Jun 2015 21:47:57 +0100	[thread overview]
Message-ID: <557C96FD.60004@youngman.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.02.1506132207180.9487@uplift.swm.pp.se>

On 13/06/15 21:11, Mikael Abrahamsson wrote:
> On Sat, 13 Jun 2015, wiebittewas wrote:
> 
>> for a larger archive, we're thinking about buying six
>> 8TB-Archive-Disks from Seagate to build a 4+2 Raid6-Array.
>>
>> now we've seen, that these disks are told not-recommended for raid,
>> because they lack ERC/TLER (like many desktop-disks)
> 
> Not only that.
> 
> You might want to read:
> 
> http://www.spinics.net/lists/linux-ide/msg50641.html
> 
> These drives are different beasts than regular HDDs, and we seem to be
> seeing problems with them just the way SSDs were problematic in the
> beginning.
> 
> So you might want to reconsider using SMR drives for RAID use. I was
> considering them until I read up on them, and then I decided it was too
> early in the deployment cycle to use them for RAID use.
> 
I didn't know these were shingled drives ... does the OP know what a
shingled drive is?

Basically, to get decent performance out of these drives, you have to
stream data at them - they're more like a tape-drive than a
random-access disk. So. They're great for backups, much less so for
normal use.

Cheers,
Wol

  reply	other threads:[~2015-06-13 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13 15:58 seagate-"archive"-disks with raid6? wiebittewas
2015-06-13 16:20 ` Wols Lists
2015-06-13 20:11 ` Mikael Abrahamsson
2015-06-13 20:47   ` Wols Lists [this message]
2015-06-16  2:58   ` wiebittewas

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=557C96FD.60004@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    --cc=wiebittewas@googlemail.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 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.