• 5 Posts
  • 376 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle















  • I also have GrapheneOS, but have been noticing that it would (for example) annoyingly kill Voyager when I’m in the middle of writing a comment and task switch to Firefox to copy a URL or something. I switch back and it’s back on the home feed with a message that it “recovered” my comment text, but of course I have no hope of finding the thing I wanted to reply to again…

    This is on a Pixel 7 that should have plenty of RAM, BTW.




  • That’s a use-case for a fuckton of total capacity, but not necessarily a fuckton of per-drive capacity. I think what the grandparent comment is really trying to say is that the capacity has so vastly outstripped mechanical-disk data transfer speed that it’s hard to actually make use of it all.

    For example, let’s say you have these running in a RAID 5 array, and one of the drives fails and you have to swap it out. At 190MB/s max sustained transfer rate (figure for a 28TB Seagate Exos; I assume this new one is similar), you’re talking about over two days just to copy over the parity information and get the array out of degraded mode! At some point these big drives stop being suitable for that use-case just because the vulnerability window is so large that the risk of a second drive failure causing data loss is too great.