- Minor
So I noticed that a user share drive listing (used for computing share size) includes pools that are set to not participate in user shares, when they happen to have the same top level folder name as those other shares.
This leads to incorrect size calculations.
Note that the folder itself however does not appear in the SMB user share (as expected), and so this is more of a cosmetic issue that also impacts utilization calculations, rather than a functional problem with user share file/folder inclusions.
User share list:
Disk share list (pool not participating in user shares):
Shares size compute detail:
