For the production PACS, reliability and uptime are far more important than speed.
Amen Brother,
Praise God the Almighty!
ZFS is used often in production, according to my limited experience, is exactly what you want/need for production.
I have not lost a single bit to ZFS problems, and I've run it on suitable and unsuitable platforms for 15+ years. I run ZFS on bare metal FreeBSD, VMWare hosted Freebsd, and I've got extensive experience on Solaris (but won't run that anymore, because Larry is a right despicable cunt.). ZFS is the file system all others oughta be. The only thing coming close is jfs on lvm in AIX. The rest, including every native Linux file system I've ever seen, is just a joke in comparison. Of course I'd rather not run it on Linux, because I'd rather not run
anything on Linux.
Had a typical interaction with Centos and it's network manager UI today. It is mostly incapable of creating a LACP paired connection. To smooth over this, the vendor who ships the application running in a bunch of bad copies of FreeBSD jails on top of the OS, ships a Python script that fails to interact with the native config UI and its backend.
Also, the LACP config CLI says to type a string in its help output, and when I type that exact string, complains that there are too many or too few parameters.
I want to hurt people.
TE update: 5316b has shipping label created. Investigating oscillator options. Perhaps should buy a 10-pack of those CTI oscillators..