February 9, 201412 yr So both exports are pointing to the same location when I try to browse them via NFS. I tried disabling all NFS shares, then NFS, then rebooting, and re-enabling everything but they are recreated in /etc/exports with same fsid. Message from syslog - Feb 9 09:12:24 Dave-San mountd[3399]: /mnt/user/Media and /mnt/user/vm_store have same filehandle for *, using first /etc/exports - "/mnt/user/Media" -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/vm_iso" -async,no_subtree_check,fsid=101 *(rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/vm_store" -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=100,anonuid=99,all_squash) Anyone know where it determines what fsid to use? This is with unRaid 5.0.5 edit: I'm sure this has something to do with it - I was trying a bunch of plugins and some personal stuff and decided to do a clean install. I didn't copy over the config files right (didn't notice dialog box open in the background opps) and when I started it back up I had to re-add the disks and readd the shares which were already existing. So I guess I messed up what ever counter it uses.
February 9, 201412 yr Author Went into /boot/config/shares and checked the files. There is a "shareExportNFSFsid=" option and I just changed it to what I wanted. This fixes it for file systems that are already there, but I tested creating a new one and it created the test one with fsid=101 which is the same as an existing entry. Anyone know where it determines the fsid to use when setting up these entries? edit: actually that didn't work. I'm confused. I changed vm_store fsid=101, and vm_iso fsid=102.. but just having vm_store exported; when I browse it, it has the contents of vm_iso. How do I just reset all of this edit2: This is like a live blog now I think ESXi was caching the nfs mounts.. rebooted it, removed the nfs mounts, re-added them and now everything looks good. Oh, and I found out where it decides on the fsid. /boot/config/share.cfg. shareNFSFsid= This looks like it determins the fsid of the next nfs export you make
Archived
This topic is now archived and is closed to further replies.