NFS: Difference between revisions
From DWIKI
mNo edit summary |
m (→FAQ) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
*[http://nfs.sourceforge.net/nfs-howto http://nfs.sourceforge.net/nfs-howto] | *[http://nfs.sourceforge.net/nfs-howto http://nfs.sourceforge.net/nfs-howto] | ||
*[https://wiki.archlinux.org/title/NFS ArchLinux NFS doc] | |||
| | ||
=Docs= | |||
==fsid== | |||
===fsid=0=== | |||
In nfs4 this is makes this export the root relative to which all others | |||
"base point under which all directories the server is exporting to a certain client are located" | |||
==nfs4.2== | |||
=HOWTO= | |||
==On server== | |||
=== show mounted exports in /proc === | |||
Not all are currently active, exportfs seems to update this | |||
cat /proc/fs/nfs/exports | |||
=== show clients === | |||
Not all are currently active | |||
cat /var/lib/nfs/rmtab | |||
=== list connected clients === | |||
IP=`ip route get 1 | awk '{print $NF;exit}'` | |||
netstat -an | grep $IP | grep 2049 | awk '{ print $5 }'| sed 's/:.*//g' | |||
= FAQ = | = FAQ = | ||
==Client== | |||
===mount.nfs: portmap query failed: RPC: Remote system error - No route to host=== | |||
Could be firewall, | |||
firewall-cmd --permanent --add-service=nfs | |||
firewall-cmd --permanent --add-service=mountd | |||
firewall-cmd --permanent --add-service=rpc-bind | |||
firewall-cmd --reload | |||
===mount.nfs: requested NFS version or transport protocol is not supported=== | |||
===portmap query retrying: RPC: Program not registered=== | |||
===mount to NFS server xxx failed: System Error: Connection refused.=== | |||
== SUNRPC: reached max allowed number (1) did not add transport to server == | |||
You might be using 2 interfaces connecting to same server | |||
== mount -t nfs taking very long == | == mount -t nfs taking very long == | ||
| Line 23: | Line 68: | ||
| | ||
== Failed: stale file handle == | == Failed: stale file handle == | ||
| Line 35: | Line 77: | ||
| | ||
== versions supported by server == | == versions supported by server == | ||
| Line 43: | Line 82: | ||
cat /proc/fs/nfsd/versions | cat /proc/fs/nfsd/versions | ||
== nfs: server 1.2.3.4 not responding, timed out== | == nfs: server 1.2.3.4 not responding, timed out == | ||
?? | ?? | ||
== mount.nfs: access denied by server while mounting == | |||
Could be wrong path in exports, maybe nfs3 vs nfs4.2 confusion? | |||
Latest revision as of 08:54, 22 May 2024
Network File System
Links
Docs
fsid
fsid=0
In nfs4 this is makes this export the root relative to which all others "base point under which all directories the server is exporting to a certain client are located"
nfs4.2
HOWTO
On server
show mounted exports in /proc
Not all are currently active, exportfs seems to update this
cat /proc/fs/nfs/exports
show clients
Not all are currently active
cat /var/lib/nfs/rmtab
list connected clients
IP=`ip route get 1 | awk '{print $NF;exit}'`
netstat -an | grep $IP | grep 2049 | awk '{ print $5 }'| sed 's/:.*//g'
FAQ
Client
mount.nfs: portmap query failed: RPC: Remote system error - No route to host
Could be firewall,
firewall-cmd --permanent --add-service=nfs firewall-cmd --permanent --add-service=mountd firewall-cmd --permanent --add-service=rpc-bind firewall-cmd --reload
mount.nfs: requested NFS version or transport protocol is not supported
portmap query retrying: RPC: Program not registered
mount to NFS server xxx failed: System Error: Connection refused.
SUNRPC: reached max allowed number (1) did not add transport to server
You might be using 2 interfaces connecting to same server
mount -t nfs taking very long
mount.nfs: No route to host
firewall, really
Failed: stale file handle
umount -fl
versions supported by server
cat /proc/fs/nfsd/versions
nfs: server 1.2.3.4 not responding, timed out
??
mount.nfs: access denied by server while mounting
Could be wrong path in exports, maybe nfs3 vs nfs4.2 confusion?
