# mount -t 192.168.1.1:/tmp /home mount.nfs4: 192.168.1.1:/tmp failed, reason given by server: No such file or directory.
My NSFv4 Server exports
/tmp 192.168.1.0/255.255.255.0(rw,no_root_squash,sync,no_subtree_check,fsid=0)
On the NFSv4 Server, I recall I export file system and restart the nfs server
# exportfs -av # service nfs start
I was having the issue, because I fail to understand the characteristics of the NFSv4. In NFSv4, it uses the virtual file system to present the server’s export and associated root filehandles to the client. The keep idea is to look what it mean fsid=0 on the NFS Server. For more information, do look at
A brief look at the difference between NFSv3 and NFSv4
The solution is to
# mount -t nfs4 192.168.1.1:/ /home
and the solution is there.
No comments:
Post a Comment