Hey everyone,

 

I just updated from 6.12.0-rc6 to 6.12.3 and noticed that exclusive shares don't work together with NFS exports (as it´s stated very clearly in the patch notes). However, the strange thing is, that this worked perfectly in 6.12.0-rc6. Maybe this is because of some last minute change that got introduced in 6.12 or I tinkered around manually with /etc/exports and just can´t remember that I did so....

 

I understand that this doesn't work with the symlinks, as they are not resolved by the NFS server, so here is my proposal:

When a share fulfills all conditions to be exclusive, but is exported via NFS. Instead of using FUSE and exporting the share via /mnt/user/myshare, what about using a symlink and exposing the share directly via e.g. /mnt/mypool/myshare?

 

This might be a little inconvenient when mounting the share, but nothing good documentation couldn't fix. Any thoughts?

 

And btw, for everyone stumbling across this, who might need the functionality already, here is how I solved it for now:

 

Disable the NFS export for all shares you want to be exclusive and create a new user script that runs on every array start and looks like this:

KUBE_STORAGE="\"/mnt/storage/KubeStorage\" -fsid=103,async,no_subtree_check 192.168.100.200(sec=sys,rw,sync,no_subtree_check,no_root_squash)"
EXPORTS="/etc/exports"

grep -qF -- "$KUBE_STORAGE" "$EXPORTS" || echo "$KUBE_STORAGE" >> "$EXPORTS"
exportfs -ra

 

Ofc, modify the path to point directly to the folder in your pool and you might want to change or remove the NFS options (everything after and including 192.168... - in particular no_subtree_check,no_root_squash) unless you know what you are doing. Repeat line 1 and 4 for each share you want to export.

Edited August 18, 20232 yr by jonpetersathan