Monthly updated new node report

[Alexey]

Since it’s zfs, this compression is more related to a record size and the really used data, see the discussion there:

Node using a lot of extra diskspace (ZFS)

So I was cleaning my server a bit, and noticed that the ZFS tank is using around 2TB more then reported. df -h reports: Filesystem Size Used Avail Use% Mounted on storage/STORJ 8.8T 4.8T 4.1T 55% /storage/STORJ Exporter Data: Total: 4.000 TB Used: 2.811 TB Trash: 49.02 GB I’m running a 32TB 4-disk raidz1. Recordsize is 1M and compression is off. Someone know the reason, why I have around 2TB missing diskspace? Or advice how to cut it down a bit?

and

Zfs discussions

my zpool for my zfs raidz1 is using 128K recordsize think that was just default settings… @kevink i don’t think you need to actually create multiple datasets or mount points to have zfs run different compression or such things on a folder… pretty sure thats mostly subject to configuration… not sure about recordsize tho… it seems like it might not be… why can’t the database just run on 1M Recordsizes?