389
“We just lost 3TB of data on a SanDisk Extreme SSD” - The Verge
(www.theverge.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Aug 2023
389 points (92.4% liked)
Technology
59147 readers
1871 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
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
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