NFS "mount system call failed"
Harald Schmalzbauer
h.schmalzbauer at omnilan.de
Wed Jan 21 10:28:01 UTC 2015
Bezüglich Märk Owen's Nachricht vom 20.01.2015 16:44 (localtime):
> Hi everyone,
>
> I'm using FreeBSD 10.1 to share a ZFS pool (mounted at /media/storage)
> through NFS to Linux clients (Debian 7). I don't seem to get any errors
> when the nfs services start on FreeBSD but I can't mount the shares on
> the clients, all I get is: mount.nfs4: mount system call failed (Tried
> as NFSv3 and NFSv4, same result).
>
> I'm really frustrated here since It worked barely an hour ago and I
> have absolutely no idea why I getting this error now.
>
> Anyway, here are my /etc/rc.conf and /etc/exports files from the server:
>
> /etc/rc.conf
> ...
> ## ZFS
> zfs_enable="YES"
> ## NFSv4 Server
> nfs_server_enable="YES"
> nfsv4_server_enable="YES"
> rpcbind_enable="YES"
> mountd_enable="YES"
> mountd_flags="-r"
> #rpc_lockd_enable="YES"
> #rpc_statd_enable="YES"
>
> /etc/exports (I tried both as NFSv3 and NFSv4, here are the two options)
> -NFSv3:
> /media/storage/data -ro -alldirs -network 192.168.1.0 -mask
> 255.255.255.0
>
> -NFSv4:
> V4:/media/storage -network 192.168.1.0 -mask 255.255.255.0
> /media/storage/data -ro -alldirs -network 192.168.1.0 -mask
> 255.255.255.0
For the nfs4 case it seems 'nfsuserd_enable="YES"' is missing in your
rc.conf (and on the client?).
If your clients don't share the same domain suffix in their fqdn, you'll
also want to set 'nfsuserd_flags="-domain your.upper.tld"'
-Harry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20150121/e0a2bc26/attachment.sig>
More information about the freebsd-stable
mailing list