Comment

Comment on “We just lost 3TB of data on a SanDisk Extreme SSD” - The Verge

This is exactly why I invested 250x the cost of one SSD into my raid setup. It’s 100 SSD’s in raid1 in a huge rack which slides vertically on 4 guide poles.

I sit under the contraption and lean forward as far as I can, before lowering it onto my back. This method allows me to suck my own cock with ease, so that I don’t need to fellate myself on public forums

source

Sort:hotnew top

Rootiest@lemmy.world ⁨1⁩ ⁨year⁩ ago

so that I don’t need to fellate myself on public forums

But you still do anyway, because you like the way it feels

source
- AttackPanda@programming.dev ⁨1⁩ ⁨year⁩ ago
  But he doesn’t HAVE TO
  
  source
  - ElPussyKangaroo@lemmy.world ⁨1⁩ ⁨year⁩ ago
    No. He doesn’t NEED to.
    
    Big difference. He can. And he probably also has to, but he just doesn’t NEED to.
    
    source
nehal3m@sh.itjust.works ⁨1⁩ ⁨year⁩ ago
I hope you’re getting off on redundancy and not a backup. Because RAID.is.not.a.backup.

source
- showmustgo@lemmy.world ⁨1⁩ ⁨year⁩ ago
  (I can even gargle my balls)
  
  source
- You999@lemmy.world ⁨1⁩ ⁨year⁩ ago
  Raid doesnt even protect against bit rot either. It doesn’t matter how many disks you write to even in a raid one array you are still vulnerable. Unless you have a high end raid card that does block level checksuming your raid array will not go back and verify previously written to data is still correct. If it does have checksuming it still isn’t smart enough to know which drive is the is correct and will lock the array in the best case.
  
  source
  - Eufalconimorph@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago
    ZFS pools do checksumming, snapshotting, etc.
    
    source
    You999@lemmy.world ⁨1⁩ ⁨year⁩ ago
    As well as BTRFS and ReFS
    
    source