NFSv4 share issues

rbees · 09-02-2015, 02:19 PM

First I want to thank in the strongest of terms the people that help others on this site.

My issue is that I am trying to set up nfs shares from my nas4free box to be accessible, via manual mount when needed, by Debian Stretch clients, a mac-book client, and possibly some android devices. With eventual goal of automating the backup process. The problem is that even though the share are configured and the connecting attempt is made the nas4free claims that there is "No such file or directory"

From the nas4free(bsd) exports file as setup by the web-portal.

Code:

V4: /mnt/crasher/kingbee -network 192.168.7.0 -mask 255.255.255.192

When trying to mount the nfs4 share from the Debian Stretch client with

Code:

:~$ sudo mount -t nfs4  nasbee:/mnt/crasher/kingbee /media/kingbee
mount.nfs4: mounting nasbee:/mnt/crasher/kingbee failed, reason given by server: No such file or directory
:~$

Yet the share is there and is writable via rsync and ssh by the user from the Debian client.

What am I missing?

hortageno · 09-02-2015, 02:44 PM

Quote:

Originally Posted by rbees

First I want to thank in the strongest of terms the people that help others on this site.

My issue is that I am trying to set up nfs shares from my nas4free box to be accessible, via manual mount when needed, by Debian Stretch clients, a mac-book client, and possibly some android devices. With eventual goal of automating the backup process. The problem is that even though the share are configured and the connecting attempt is made the nas4free claims that there is "No such file or directory"

From the nas4free(bsd) exports file as setup by the web-portal.

Code:

V4: /mnt/crasher/kingbee -network 192.168.7.0 -mask 255.255.255.192

When trying to mount the nfs4 share from the Debian Stretch client with

Code:

:~$ sudo mount -t nfs4  nasbee:/mnt/crasher/kingbee /media/kingbee
mount.nfs4: mounting nasbee:/mnt/crasher/kingbee failed, reason given by server: No such file or directory
:~$

Yet the share is there and is writable via rsync and ssh by the user from the Debian client.

What am I missing?

What's the IP of your PC?

rbees · 09-02-2015, 03:58 PM

the ip is in the network sub-net that is specified in the n4f exports

hortageno · 09-02-2015, 04:04 PM

Quote:

Originally Posted by rbees

the ip is in the network sub-net that is specified in the n4f exports

That's not the answer to my question. There might might be a typo somewhere, for instance in the subnet mask.

rbees · 09-02-2015, 04:12 PM

Nope, its the same as dhcpd.conf on the dhcp server for the whole sub-net

The exports file in the n4f is generated by the web-portal so as long as the data is entered correctly it should be ok.

sgrlscz · 09-03-2015, 06:55 AM

I don't do a lot with BSD, but I think to your exports file needs to be changed to:

Code:

/mnt/crasher/kingbee -network 192.168.7.0 -mask 255.255.255.192
V4: / -network 192.168.7.0 -mask 255.255.255.192

The V4 line sets the root of the nfsv4 tree, and there can only be one nfsv4 root. So, you can have multiple V4 lines (to set security settings, etc. for different systems/networks), but they all must have the same root.

rbees · 09-03-2015, 07:32 AM

Thanks sgrlscz,

I played with the settings in the web-portal some more and got to work by getting rid of all the v4 stuff.

When I have time to really look into it maybe I can figure out why it was not working.