this post was submitted on 07 Aug 2023
123 points (100.0% liked)

Technology

37740 readers
720 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] argv_minus_one@beehaw.org 3 points 1 year ago (1 children)

True, but it will protect you from a single drive failing like this.

[–] Dominic@beehaw.org 2 points 1 year ago (1 children)

I don’t think the drive actually failed. The article said that the files disappeared from the drive one-by-one, which sounds like a firmware bug to me.

You could theoretically have the same problem due to a buggy RAID controller or driver.

[–] argv_minus_one@beehaw.org 1 points 1 year ago

I don’t think the drive actually failed. The article said that the files disappeared from the drive one-by-one

It didn't fail in the sense of reporting an I/O error, but it did fail in the sense that the bytes previously written to it can't be read any more.

which sounds like a firmware bug to me.

Could be. SSD firmware is pretty notorious for data loss.

You could theoretically have the same problem due to a buggy RAID controller or driver.

Which is why I don't trust hardware RAID controllers, only software RAID, preferably with per-block checksums so that the software RAID controller knows which copy is the good copy.

The author is using macOS, whose APFS file system has those features. Linux's btrfs does too.