Difference between revisions of "Mount a remote nfs share"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
(13 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | Mounting using hostname instead of IP address can solve some of errors reported in this page | ||
+ | |||
+ | |||
[[mount -t nfs]] -o proto=tcp,port=2049 REMOTE_IP_SERVER:/REMOTE_SHARE_DIR /YOUR/LOCAL_DIR/ | [[mount -t nfs]] -o proto=tcp,port=2049 REMOTE_IP_SERVER:/REMOTE_SHARE_DIR /YOUR/LOCAL_DIR/ | ||
− | mount -t nfs4 10.10.10.2:/ ./ | + | [[mount -t nfs4]] 10.10.10.2:/ ./ |
mount: /mnt: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program | mount: /mnt: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program | ||
(Install client: <code> apt-get install [[nfs-common]]</code>) | (Install client: <code> apt-get install [[nfs-common]]</code>) | ||
mount.[[nfs4]]: requested NFS version or transport protocol is not supported | mount.[[nfs4]]: requested NFS version or transport protocol is not supported | ||
+ | |||
+ | Solution: Try to mount it using hostname instead of IP | ||
+ | |||
+ | mount.nfs: [[portmap]] query retrying: [[RPC]]: Program not registered | ||
mount -v -t nfs4 10.10.10.2:/ ./ | mount -v -t nfs4 10.10.10.2:/ ./ | ||
Line 26: | Line 33: | ||
Apr 22 09:28:34 your_hostname kernel: RPC: Registered named UNIX socket transport module. | Apr 22 09:28:34 your_hostname kernel: RPC: Registered named UNIX socket transport module. | ||
Apr 22 09:28:34 your_hostname kernel: FS-Cache: Loaded | Apr 22 09:28:34 your_hostname kernel: FS-Cache: Loaded | ||
+ | |||
+ | == Activities == | ||
+ | * Read about EFS performance settings https://docs.aws.amazon.com/efs/latest/ug/performance.html#performance-tips | ||
+ | Don't use the following mount options: | ||
+ | * <code>[[noac]], [[actimeo]]=0, [[acregmax]]=0, [[acdirmax]]=0</code> – These options disable the attribute cache, which has a very large performance impact. | ||
+ | * <code>[[lookupcache]]=pos, [[lookupcache]]=none</code> – These options disable the file name lookup cache, which has a very large impact on performance. | ||
+ | * <code>[[fsc]]</code> – This option enables local file caching, but does not change NFS cache coherency, and does not reduce latencies. | ||
== Related terms == | == Related terms == | ||
+ | * <code>[[exportfs]]</code> List exported filesystems | ||
* <code>[[mount]]</code> | * <code>[[mount]]</code> | ||
* [[RPC]] | * [[RPC]] | ||
+ | * <code>[[systemctl status]] nfs-server</code> | ||
== See also == | == See also == | ||
+ | * {{mount}} | ||
* {{NFS}} | * {{NFS}} | ||
[[Category:Computing]] | [[Category:Computing]] |
Latest revision as of 06:43, 25 May 2023
Mounting using hostname instead of IP address can solve some of errors reported in this page
mount -t nfs -o proto=tcp,port=2049 REMOTE_IP_SERVER:/REMOTE_SHARE_DIR /YOUR/LOCAL_DIR/
mount -t nfs4 10.10.10.2:/ ./
mount: /mnt: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program
(Install client: apt-get install nfs-common
)
mount.nfs4: requested NFS version or transport protocol is not supported
Solution: Try to mount it using hostname instead of IP
mount.nfs: portmap query retrying: RPC: Program not registered
mount -v -t nfs4 10.10.10.2:/ ./ mount.nfs4: timeout set for Wed Apr 22 09:55:59 2020 mount.nfs4: trying text-based options 'vers=4.2,addr=0.10.10.22:,clientaddr=10.10.10.2:' mount.nfs4: mount(2): No route to host
mount -v -t nfs -o vers=3,timeo=600,noresvport,nolock 10.10.10.2:/ /local/path
Contents
Logs[edit]
Apr 22 09:28:34 your_hostname kernel: Key type id_legacy registered Apr 22 09:28:34 your_hostname kernel: Key type id_resolver registered Apr 22 09:28:34 your_hostname kernel: NFS: Registering the id_resolver key type Apr 22 09:28:34 your_hostname kernel: FS-Cache: Netfs 'nfs' registered for caching Apr 22 09:28:34 your_hostname kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Apr 22 09:28:34 your_hostname kernel: RPC: Registered tcp transport module. Apr 22 09:28:34 your_hostname kernel: RPC: Registered udp transport module. Apr 22 09:28:34 your_hostname kernel: RPC: Registered named UNIX socket transport module. Apr 22 09:28:34 your_hostname kernel: FS-Cache: Loaded
Activities[edit]
- Read about EFS performance settings https://docs.aws.amazon.com/efs/latest/ug/performance.html#performance-tips
Don't use the following mount options:
noac, actimeo=0, acregmax=0, acdirmax=0
– These options disable the attribute cache, which has a very large performance impact.lookupcache=pos, lookupcache=none
– These options disable the file name lookup cache, which has a very large impact on performance.fsc
– This option enables local file caching, but does not change NFS cache coherency, and does not reduce latencies.
Related terms[edit]
exportfs
List exported filesystemsmount
- RPC
systemctl status nfs-server
See also[edit]
- File systems:
mount
,umount
,findmnt
,find
,swapon
,swapoff
,UUID, blkid
, mount options:/etc/fstab
,udisksctl mount
,guestmount
,/proc/mounts
,fstrim
,systemd-mount
,defaults
- NFS:
nfs-common
,nfstat
,nfsiostat
,sar -n NFS
, Mount a remote nfs share,mount
,showmount
,exportfs
,rpcinfo
, List mounted NFS resources, RPC, AWS EFS
Advertising: