public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Seagate hard drives with dual actuators.
Date: Thu, 14 Nov 2024 17:10:50 -0600	[thread overview]
Message-ID: <63e3fac6-1758-b5c2-2c92-312d64d547e3@gmail.com> (raw)
In-Reply-To: <CAGfcS_=vkPA=MsiD0Jk-qMO48XngHr8jL_DviFDE1P3aLDXJUg@mail.gmail.com>

Rich Freeman wrote:
> On Thu, Nov 14, 2024 at 3:33 PM Dale <rdalek1967@gmail.com> wrote:
>>
>> I've had a Seagate, a Maxtor from way back and a Western Digital go bad.  This is one reason I don't knock any drive maker.  Any of them can produce a bad drive.
> ++
>
> All the consumer drive manufacturers are in a super-price-conscious
> market.  For the most part their drives work as advertised, and
> basically all of them have made a model with an abysmal failure rate
> at some point.  I think Backblaze still publishes their stats and I
> don't think any manufacturer stood out when it comes to these cheaper
> consumer drives.  The enterprise stuff probably is more reliable, but
> for HDD I don't think it is worth it - just use RAID.
>
> I've personally been trying to shift towards solid state.  Granted, it
> is about double the price of large 5400RPM drives, but the performance
> is incomparable.  I've also been moving more towards used enterprise
> drives with PLP/etc and where I can find the drive endurance info on
> the ebay listing.  You can typically pay about $50/TB for an
> enterprise SSD - either SATA or NVMe.  You'll pay a bit more if you
> want a high capacity drive (U.2 16+TB or whatever).  That's in part
> because I've been shifting to Ceph which is pretty IOPS-sensitive.
> However, it is nice that when I add/replace a drive the cluster
> rebuilds in an hour at most with kinda shocking network IO.
>
> I'll use cheap consumer SATA/M.2 SSDs for OS drives that are easily
> reimaged.  I'll use higher performance M.2 for gaming rigs (mostly
> read-oriented), and back it up.  Be aware that the consumer write
> benchmarks only work for short bursts and fall to a fraction of the
> advertisement for sustained writes - the enterprise write benchmarks
> reflect sustained writes and you can run at that speed until the drive
> dies.
>


The biggest downside to the large drives available now, even if SMART
tells you a drive is failing, you likely won't have time to copy the
data over to a new drive before it fails.  On a 18TB drive, using
pvmove, it can take a long time to move data.  I think the last time I
did it, it took like two days.  Usually SMART is more like a 24 hour
warning.  Of course with some failures, you get no warning at all. 
SMART can't detect all modes of failure. 

Wol has a good point too.  What they trying to do is compete with SSD if
they can.  SSD, NVME and such are pricey if you need to store bulk
amounts of data.  I don't even want to think what it would cost to put
all my 100TBs or so on SSD or NVME drives.  WOW!!! 

Dale

:-)  :-) 


  reply	other threads:[~2024-11-14 23:11 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 23:10 [gentoo-user] Seagate hard drives with dual actuators Dale
2024-11-14  0:46 ` Matt Jolly
2024-11-14 13:05   ` Dale
2024-11-14  7:55 ` Wols Lists
2024-11-14 16:48   ` Dale
2024-11-15  0:18     ` [OT] " Peter Humphrey
2024-11-15  8:41       ` [gentoo-user] Hollerith (was: Seagate hard drives with dual actuators) karl
2024-11-15  9:51       ` [OT] Re: [gentoo-user] Seagate hard drives with dual actuators Wols Lists
2024-11-14 11:21 ` Michael
2024-11-14 17:00   ` Dale
2024-11-14 19:12     ` Michael
2024-11-14 19:51       ` Frank Steinmetzger
2024-11-14 19:55         ` Frank Steinmetzger
2024-11-14 23:14           ` Peter Humphrey
2024-11-14 20:33       ` Dale
2024-11-14 20:57         ` Rich Freeman
2024-11-14 23:10           ` Dale [this message]
2024-11-15  0:59             ` Rich Freeman
2024-11-15  5:53               ` Dale
2024-11-15 10:09                 ` Michael
2024-11-15 11:59                   ` Dale
2024-11-15 15:35                     ` Michael
2024-11-15 16:36                       ` Dale
2024-11-15 22:13                       ` Rich Freeman
2024-11-16 11:02                         ` Michael
2024-11-16 14:36                           ` Rich Freeman
2024-11-16 19:47                             ` Michael
2024-11-16 20:13                               ` Rich Freeman
2024-11-16 23:21                                 ` Wol
2024-11-17 11:22                                 ` Michael
2024-11-17 21:26                                   ` Rich Freeman
2024-11-17 23:04                                     ` Jack
2024-11-18  0:23                                       ` Rich Freeman
2024-11-18  2:32                                         ` Matt Jolly
2024-11-15 10:38                 ` Frank Steinmetzger
2024-11-15 12:19                   ` Dale
2024-11-14 22:38         ` Wols Lists
2024-11-15  9:35           ` Michael

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=63e3fac6-1758-b5c2-2c92-312d64d547e3@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.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