Why is the repo 300% larger than the source folder?

@alexweiss I understand your logic, but the problem is that the source zfs filesystem is only showing a 1.4x compression ratio, whereas the destination is showing a 1.9x compression ratio. Assuming the actual data size is the same on both, the apparent size on the destination should be less than the apparent size on the source.

@GuitarBilly Normally, the daily change rate of the data would be fractional, like maybe 1%, However, I have a theory about what may be happening that I will check into.

@rawtaz

db_rsyncs is not its own filesystem, just a sub-folder under /zpool, so I don’t know if this will tell you much…

On the source server, STORE50B

[root@store50b zpool0]# zfs list -tall
NAME USED AVAIL REFER MOUNTPOINT
zpool0 10.9T 3.50T 10.9T /zpool0

On the dest server, STORE50A

[root@store50a ~]# zfs list -tall
NAME USED AVAIL REFER MOUNTPOINT
zpool0 4.86T 9.50T 4.86T /zpool0

Let’s stand down for a couple of days on this while I monitor the behavior some more and explore a possible theory I have about what’s happening.

1 Like

I think you might find better help about this in a zfs forum or on some other zfs platform.

If you are uncertain about the real size of the files, please try

find . -type f -exec cat {} + | wc -c