News for hackers. Stuff that matters.
Re:SSDs: A gift and a curse by yellowapple on Tuesday June 02, 2015 @03:03PM (#9648181)
Parts of this sound more like hardware RAID controller issues than SSD issues, which is why I typically avoid hardware RAID in production environments unless there's a specific reason for it. RAID controllers tend to be buggy pieces of shit, usually implementing some RAID method that's more-or-less proprietary and unique even between different RAID cards from the same vendor (meaning that if your RAID controller fails, you might as well kiss your data goodbye, since the replacement - 9 times out of 10 - won't be able to make sense of its predecessor's RAID setup).

Also, RAID6 is a bad idea, almost as bad as RAID5. There have been numerous studies and reports [0] indicating that both are very susceptible to subtle bit errors ("cosmic rays"), and this is made even worse when SSDs are involved. If you need absolute data integrity, RAID1 is your only option; if you need a balance between integrity, performance, and capacity, go with RAID10, which is still leaps-and-bounds better than RAID5/6.

[0]: http://www.miracleas.com/BAARF/Why_RAID5_is_bad_news.pdf

Re:SSDs: A gift and a curse by JoeAltmaier on Tuesday June 02, 2015 @03:12PM (#9648228)
To expand: in my 20-year experience, no small-computer RAID 5/6 controller I have had experience with has ever saved any data, ever. All failures are hard and non-recoverable. Which begs the question: why use them at all? I mirror only.
Re:SSDs: A gift and a curse by Laforet on Tuesday June 02, 2015 @07:35PM (#9649700)
RAIDs are in place to for your guaranteed uptime in the SLA. With the current storage density RAID5/6 is probably more fragile than single disks because UREs are very likely during a rebuild. Nonetheless having a degraded array is probably better than having an offline system and it will buy you some time to migrate. Mirrors are ideal, but it is hard to justify the upfront cost.
Re:SSDs: A gift and a curse by yellowapple on Wednesday June 03, 2015 @02:38PM (#9654807)
If you're trying to maintain guaranteed uptime, you're probably better off with machine-level redundancy rather than disk-level redundancy.

> Mirrors are ideal, but it is hard to justify the upfront cost.

The upfront cost of redundant backups can also be high, but that doesn't mean one should forego them (unless their data isn't worth it, in which case, why bother collecting it?).

Going cheap on things is fine in the home computing realm, but once you're in the business realm, going cheap almost inevitably becomes more expensive in the long run.

Re:SSDs: A gift and a curse by JoeAltmaier on Wednesday June 03, 2015 @09:23AM (#9652301)
For small home machines, the storage cost is minimal. All my home machines are mirrored, for around $100 each. Its saved me several times.
Re:SSDs: A gift and a curse by cerberusss on Thursday June 04, 2015 @06:18AM (#9658330)
I've never understood this. At home, you don't need uptime, thus you're much better off with a real offline backup instead of a mirror.
Re:SSDs: A gift and a curse by yellowapple on Thursday June 04, 2015 @02:06PM (#9660960)
You don't need uptime, but it's nice to have. Repairing a degraded mirror takes a lot less time than restoring from a backup in the vast majority of cases.
Re:SSDs: A gift and a curse by bbulkow on Tuesday June 02, 2015 @06:32PM (#9649474)
I have seen data recovery. Once. 22 years into my career, and it was still a home system. Which I believe proves your point.
Re:SSDs: A gift and a curse by rsync on Tuesday June 02, 2015 @03:50PM (#9648480)
A modern filesystem, like ZFS, will protect against random bit errors.

Raid 5/6 are still not appropriate for todays large disk sizes, but raidz3 (three parity disks instead of one or two) is.

Re:SSDs: A gift and a curse by yellowapple on Tuesday June 02, 2015 @06:32PM (#9649472)
Depending on the size of the array, however, even having three parity disks is likely insufficient. Using parity instead of mirroring (or a mirroring+striping approach like RAID10) - i.e. RAID3, RAID5/6, and (IIRC) RAID-Z - assumes that disk failures are rare; in reality, the probability of subsequent disk failures increases significantly once one disk failure occurs (which makes sense: unless you're mixing/matching vendors (which has its own problems), you're probably buying a lot of disks at the same time, probably from the same or similar batches, and therefore with the same failure tendencies). For things like SANs and other large arrays of disks (where the use of ZFS is more prevalent), the difference in safety between two and three parity disks is negligible. You could keep adding more and more, but at that point, you might as well just use RAID10. If you're running a smaller array, you also might as well just use RAID10 (or RAID1 if you only have 2 disks in the array, but that's playing it dangerous for the same reason why RAID5/6/Zx is playing it dangerous).

This is part of the reason why ZFS supports a variety of different RAID and RAIDlike configurations. If you're using a pure-ZFS approach, I'd strongly recommend having zpool create striped mirrors (i.e. RAID10) in order to get the benefits of ZFS' data checksumming and not be susceptible to such a high risk of data loss.