So today I wanted to create a couple of nested filesystems in ZFS so I can snapshot smaller subsets of the data. When doing this, I noticed that upon creation of a nested filesystem, all shares that were originally pointing to the parent filesystem now point to the nested filesystem (as the parent "device").
It's easy enough to fix, just switch back to the actual parent device, but why this behaviour? What is the use-case of automatically changing the share to the newly created (and therefore empty) filesystem?
Example:
I have a ZFS filesystem called "Camera" on the main ZFS Pool:
MainZFS/Camera
This is shared as a shared folder and then via SMB to all my clients. Additionally, another regular folder within the share called "Video" (MainZFS/Camera/Video) is a shared folder.
I create a sub-filesystem called "RAWs" there and mount it to, say "MainZFS/Camera/Temp/RAWs", using the Plugin:
MainZFS/Camera/RAWs
Now what happens, is that all shares originally referencing MainZFS/Camera now reference the "device" MainZFS/Camera/RAWs and therefore all shared folders now end up being shared on the location "MainZFS/Camera/Temp/RAWs"... This means obviously nothing is being shared anymore and new empty folders are created in that new filesystem instead.
Again, it seems like there is some purpose behind this, but I really can't figure out what the purpose of this would be?