You are not logged in.
Here is my /etc/exports file on my server (arch).
/mnt/data 192.168.0.1/24(rw,fsid=0,all_squash,anonuid=1001,anongid=0,async,no_subtree_check)
/mnt/data/media 192.168.0.1/24(rw,all_squash,anonuid=1001,anongid=0,async,nohide,no_subtree_check)
/mnt/data/backup 192.168.0.1/24(rw,all_squash,anonuid=1001,anongid=0,async,nohide,no_subtree_check)
Here is my /etc/fstab on the client (arch)
# NFS Mounts
192.168.0.104:/mnt/data/media /mnt/media nfs4 rsize=8192,wsize=8192,timeo=14,intr,_netdev,users 0 0
192.168.0.104:/mnt/data/backup /mnt/backup nfs4 rsize=8192,wsize=8192,timeo=14,intr,_netdev,users 0 0
According to the NFS guide, I should be exporting my root (/mnt/data) and using the fsid=0 option.
When I do this, my clients say
mount.nfs4: mounting 192.168.0.104:/mnt/data/media failed, reason given by server:
No such file or directory
If I comment that line out, everything works fine.
Does anyone know why this is behaving this way/do I really need to export the root?
Thanks,
Matt
Offline
with fsid=0 option.
$ mount -t nfs4 192.168.0.104:/ DEST # to mount the root /mnt/data
$ mount -t nfs4 192.168.0.104:/media DEST # to mount /mnt/data/media
Last edited by GutenYe (2014-01-04 10:13:23)
Linux, Vim, Ruby, Javascript and Go.
Offline