Hacker News Reader

For new data, you can get back most of that lost space by setting the recordsize to 1M. You won't necessarily see the improvement in your df and zfs list commands, as they assume smaller max recordsize, but your overhead should drop significantly.

I didn't even consider this. Thanks for the explanation! Makes tons of sense!

Incidentally, many modern filesystems (including NTFS) store very small files in the FAT rather than taking up a whole block for this very reason!

cringes at "in the FAT" instead of "MFT"....

ZFS has this same feature, however, as long as feature@embedded_data=enabled ;)

I guess I'm an old storage guy. I call it the FAT on everything! :-)

Yeah, different filesystem calls things differently FAT, MFT, inodes.

Best is to just call it metadata :)

Thanks!