this post was submitted on 21 Jan 2025
204 points (98.6% liked)

Technology

60704 readers
3905 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] somedev@aussie.zone 13 points 13 hours ago (16 children)

I would not risk 36TB of data on a single drive let alone a Seagate. Never had a good experience with them.

[–] ByteOnBikes@slrpnk.net 5 points 9 hours ago (5 children)

Ignoring the Seagate part, which makes sense... Is there a reason with 36TB?

I recall IT people losing their minds when we hit the 1TB, when the average hard drive was like 80GB.

So this growth seems right.

[–] schizo@forum.uncomfortable.business 6 points 7 hours ago (1 children)

It's raid rebuild times.

The bigger the drive, the longer the time.

The longer the time, the more likely the rebuild will fail.

That said, modern raid is much more robust against this kind of fault, but still: if you have one parity drive, one dead drive, and a raid rebuild, if you lose another drive you're fucked.

[–] notfromhere@lemmy.ml 1 points 3 hours ago

Just rebuilt onto Ceph and it’s a game changer. Drive fails? Who cares, replace it with a bigger drive and go about your day. If total drive count is large enough, and depends if using EC or replication, it could mean pulling data from tons of drives instead of a handful.

load more comments (3 replies)
load more comments (13 replies)