Not sure if this is just a oddity of the Fuse file-system or how inodes handled by autotier.
I have autotier in a docker container on truenas-scale so the underlying storage is ZFS it's mounted by nextcloud but also netdata for it's persistent storage.
Netdata thinks i'm nearly out of Inodes on the tier mount(97.1% used) and I'm trying to figure out if this is truly the case or just a quirk of autotier (I.e is it reporting real Inode availability or just a made up number).
The Bind mounts work other than not being able to use them as a SMB share in truenas (Truenas enforces using a ZFS datavol)
Not sure if this is just a oddity of the Fuse file-system or how inodes handled by autotier.
I have autotier in a docker container on truenas-scale so the underlying storage is ZFS it's mounted by nextcloud but also netdata for it's persistent storage.
Netdata thinks i'm nearly out of Inodes on the tier mount(97.1% used) and I'm trying to figure out if this is truly the case or just a quirk of autotier (I.e is it reporting real Inode availability or just a made up number).
The Bind mounts work other than not being able to use them as a SMB share in truenas (Truenas enforces using a ZFS datavol)