All right, this is extremely weird.

root@server:~# showmount -e
Export list for server:
/mnt/user/qbittorrent *
/mnt/user/discord     *
/mnt/user/backups     *

Tested from multiple CentOS VMs, if I mount /mnt/user/discord, it actually mounts /mnt/user/backups. However, if I mount /mnt/user/discord/something, it correctly mounts the discord sub-folder. I've seen weird things but this...

 

What I've tried: restarting the NFS service, rebooting the VMs, manually mounting the NFS vs using /etc/fstab, disabling the discord NFS share and reenabling it... that doesn't work. What works however is disabling the backups NFS share. If I disable it, without even having to umount /mnt/user/discord, it now correctly points to the correct directory. If I enable the backups NFS share again? /mnt/user/discord mounted on my VM now points on the backups share. I'm so confused.

 

Have you ever seen something like that? Is there some sort of file on unRAID I can see more info about NFS share configuration?

Edited June 6, 20197 yr by dnLL

It seems like they have the same ID.

 

root@server:~# exportfs -v
/mnt/user/backups
                <world>(rw,async,wdelay,hide,no_subtree_check,fsid=100,anonuid=99,anongid=100,sec=sys,insecure,root_squash,all_squash)
/mnt/user/discord
                <world>(rw,async,wdelay,hide,no_subtree_check,fsid=100,anonuid=99,anongid=100,sec=sys,insecure,root_squash,all_squash)
/mnt/user/qbittorrent
                <world>(rw,async,wdelay,hide,no_subtree_check,fsid=101,anonuid=99,anongid=100,sec=sys,insecure,root_squash,all_squash)

 

How is that possible? can it be fixed without deleting the share and/or rebooting?

Hotfixed the mounted share by editing the fsid directly into /boot/config/shares/*.cfg files. However if I create a new NFS share it takes the fsid 101, no matter what I have in /boot/config/share.cfg. There must be something somewhere else?

Potential solution: 

I assume the /boot/config/share.cfg is loaded in RAM so editing it there without restarting the array doesn't quite fix it completely for newly created shares. I assume.