de-dupe in ZFS is a "here be dragons" sort of feature, best left alone unless you're already familiar with ZFS administration and understand the tradeoffs it br

de-dupe in ZFS is a "here be dragons" sort of feature, best left alone unless you're already familiar with ZFS administration and understand the tradeoffs it brings [0] in this case, the files being stored are compressed archives (NAR files) so the block-level dedupe that ZFS does would probably find very little to work with, because the duplicated content would be at different offsets within each archive. beyond that, there's also the issue that they would need a single ZFS pool with 500TB+ of storage (given the current ~425TB size). that's certainly doable with ZFS, but the hardware needed for that server would be...non-trivial. and of course that's just a single host, they would want multiple of those servers for redundancy. distributed object storage like S3 is a much better fit for that volume of data. 0: https://www.truenas.com/docs/references/zfsdeduplication/#costs https://www.truenas.com/docs/references/zfsdeduplication/#co...