(I mean this as an honest question, I'm interested to know if there are performance or reliability gains to be had from a hardware controller)
Also, these machines were built by DB people, who have traditionally placed a lot of value in hardware RAID controllers, and to be fair, the HP controllers worked well with HDDs. Also ZFS wasn't a realistic option for production Linux in 2013. Me personally, I'm not a fan of exotic proprietary hardware, I much prefer working with JBOD disk setups and software RAID where appropriate.
Don't all enterprise SSDs come with their own backup capacitors?
Yes, but the cost of such drives makes rolling the dice with consumer grade drives appealing to some[1].
From the same thread, here's a word of warning from a Stackoverflow devops engineer[2] wrt to lack of capicitors on consumer grade drives and the perfect storm that can occur when UPS goes down in a power failure (unlike with spinning disks hardware RAID is unable prevent data corruption/loss in this case).
[1] https://laur.ie/blog/2015/06/ssds-a-gift-and-a-curse/
[2] https://laur.ie/blog/2015/06/ssds-a-gift-and-a-curse/#commen...
I don't think that professional devices are 100% fail-proof either. I vaguely remember some test where they setup a test with forced power failures during heavy writes, and they zapped all drives but a few eventually.
Something that worried me was that the failure mode quite often seemed to be a totally bricked SSD.
The fine-print is important here. Crucial (IIRC) advertises some of its low-end consumer series with power-loss protection… against internal data corruption of the Flash Translation Layer. AKA "We won't completely brick the entire device if you pull power!" Err… thank you? Why are you advertising this as feature?
What is the point of all that complication if the block device is just going to throw away those guarantees? If we're giving up on power loss safety I can make a super fast filesystem by making fsync a no-op and keeping everything in ram until I feel like writing it.
Same with HDDs. That's why battery-backed hardware RAIDs (+ disabling this cache on the connected disks) are a thing in the first place.
> What is the point of all that complication if the block device is just going to throw away those guarantees?
Ask that storage manufacturers.
Or would this functionality somehow be counteracted by a cache inside the SSD?
Perhaps filesystems should include a "ssd" mount option, because there might be more things to worry about (for example frequent writes wearing out the device).
They do. You can, for instance, mount a UFS filesystem "sync", which means that all writes are synchronous. I assume extX has a similar option ...
Also be careful with sync on SSD media; this is what the mount manpage says about the sync option:
> In case of media with limited number of write cycles (e.g. some flash drives) "sync" may cause life-cycle shortening.
The HP RAID controller failed to detect corrupted writes on what I seem to remember were Intel SSDs. The only way we learned about failed SSD drives is when we started catching large numbers of DB page checksum errors, and by that time it was too late to do anything about it.
Operationally it sucked, swapping out drives is a lot easier maintenance than having to rebuild a DB from backup.