SMB and Nested Datasets - is it a no no?

TrueNAS General
, ,
1

Hi (and happy new year)!

Issue:

One of my SMB shares with nested datasets doesn’t report the total space and used space correctly in windows explorer.

Soluton in Core:

I solved this then by appending an SMB additional parameter zfs_core:zfs_space_enabled = true as per this post.

Moving from CORE U6 to SCALE 24.10 SMB aux parameters have been removed and I have removed them before upgrading.

Question:

A) Is there any equivalent workaround in Scale or is it a windows shortcoming with ZFS as shown here?

B) Given that all my SMB shares with non-nested datasets are reported correctly, are nested datasets outside the correct usage scope of SMB in truenas? The Docs seems to hint at this, if I understood the warning, but I’d like some extra confirmation. I had used them because I could set recursive snapshots of the parent dataset.

Thanks (for both the insight and bearing with me)!

2

Currently stuck at the same point. Apart from that each subdataset of a SMB-shared Dataspace with recycle bin receives it’s own recycle bin folder as per description:
" The files are renamed to a per-user subdirectory within .recycle directory at either (1) root of SMB share (if path is same dataset as SMB share) or (2) at root of current dataset if we have nested datasets. Because of (2) there is no automatic deletion based on file size."

I wish this behaviour could be changed.
The the current point I just feel like: SMB with nested datasets do not work well together.