This is a really minor issue, but I’ve noticed that the total space reported in Windows is way out of whack. See the ones in yellow
I guess snapshots are causing some kind of weird reporting of space? All of these are on the same dataset. Any way to get it to report the correct max size, which is closer to 12TB?
Ask Samba (whích I guess is what you’re using)?
I assume the physical storage is zfs based.
Am I right to assume the following amount of usage?
V: 0.01TB
W: 0.07TB
X: 1.61TB
Z: 0.10TB
This would be following the zfs logic, where every share has access to the same amount of free space. And the max usable storage consists of the remaining free space, so the total storage for that share would be the current usage + free remaining. E.g. share V: can never reach a total of 12TB because most of that is already occupied by other zfs datasets - it can at most reach 3.75TB.
Not sure what your meaning, ask Samba? How?
is this bug on TrueNAS Scale (debian) or CORE (freebsd)?
It’s Samba that’s handles the communication between Windows and your NAS.
