> "you needs lots of RAM" is bogus. Depends on what performance you expect to get out of ZFS. I have 4GB in my NAS at home and 12TB of raw disk. It works fine

> "you needs lots of RAM" is bogus. Depends on what performance you expect to get out of ZFS. I have 4GB in my NAS at home and 12TB of raw disk. It works fine for my needs. I wouldn't use this setup for production as my I/O isn't great unless it's sequential. HAMMER deduplication only requires ~512MB RAM per 1TB you dedup. The rule of thumb for ZFS is generally 5GB RAM for 1TB of dedup. This is documented on the FreeBSD ZFS wiki. https://wiki.freebsd.org/ZFSTuningGuide https://wiki.freebsd.org/ZFSTuningGuide > Well known data base degradation (not suitable to keep SQL data bases). He's talking about performance degrading due to multiple layers of logs/journaling. If you configure your ZFS filesystem and database correctly this isn't a problem. > No file grained journaling like hammer history. He's talking about the fact that with HAMMER you can basically undelete individual files ... forever (assuming you have enough disk space). You don't need to manually do a snapshot; it retains the ability to undelete anything if you let it. > Native encryption for ZFS has been only available in Oracle version. Native encryption as implemented by Oracle is likely vulnerable to watermarking attacks. You also only mentioned L2ARC once and overlooked that simply adding an L2ARC requires more RAM. A memory constrained system can actually lose performance simply by adding a large L2ARC. Most people don't know this as it's not widely documented.