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
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.
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
But you still do anyway, because you like the way it feels
But he doesn’t HAVE TO
No. He doesn’t NEED to.
Big difference. He can. And he probably also has to, but he just doesn’t NEED to.
I hope you’re getting off on redundancy and not a backup. Because RAID.is.not.a.backup.
(I can even gargle my balls)
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.
ZFS pools do checksumming, snapshotting, etc.
As well as BTRFS and ReFS