ECS: NFS Mount Failure; UI Export Settings Take a While to Propagate
Summary: On the ECS, the NFS Cache takes ~20 minutes to propagate and refresh the NFS cache in the dataheadsvc service on the ECS appliance. This issue often occurs during a setup of a new NFS export as some changes are needed to resolve an export customization. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Instructions
On the ECS, the NFS Cache takes ~20 minutes to propagate and refresh the NFS cache in the dataheadsvc service on the ECS appliance. This issue often occurs during a setup of a new NFS export as some changes are needed to resolve an export customization.
This Behavior is expected on the ECS when an existing NFS export is modified and the export is showing as active on the ECS.
# showmount -e <IP Address of the ECS>
Example:
# mount -vv -t nfs -o vers=3,,nolock,sec=sys,proto=tcp <ECS IP>:<Export Path> <local Mount Point>
Example:
# svc_log -i -f nfs -sr all -sn -sf -n all -start '5 minutes ago'
Example:
# mount -vv -t nfs -o vers=3,,nolock,sec=sys,proto=tcp <ECS IP>:<Export Path> <local Mount Point>
Example:
This Behavior is expected on the ECS when an existing NFS export is modified and the export is showing as active on the ECS.
- To validate, having this issue check the export present on the ECS:
# showmount -e <IP Address of the ECS>
Example:
[root@nfsclient ~]# showmount -e xxx.xxx.xxx Export list for xxx.xxx.xxx.xxx: /namespace/nfsbucket *
- Attempt to mount the export that has been validated on the ECS:
# mount -vv -t nfs -o vers=3,,nolock,sec=sys,proto=tcp <ECS IP>:<Export Path> <local Mount Point>
Example:
[root@ nfsclient ~]# mount -vv -t nfs -o vers=3,,nolock,sec=sys,proto=tcp xxx.xxx.xxx.xxx:/namespace/nfsbucket /mnt/test mount.nfs: timeout set for Wed Aug 14 09:37:03 2019 mount.nfs: trying text-based options 'vers=3,nolock,sec=sys,proto=tcp,addr= xxx.xxx.xxx.xxx ' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying xxx.xxx.xxx.xxx prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=6 mount.nfs: trying xxx.xxx.xxx.xxx prog 100005 vers 3 prot TCP port 2049 mount.nfs: mount(2): No such file or directory mount.nfs: mounting xxx.xxx.xxx.xxx:/namespace/nfsbucket failed, reason given by server: No such file or directory
- Validate on the ECS the export cannot be located:
# svc_log -i -f nfs -sr all -sn -sf -n all -start '5 minutes ago'
Example:
admin@ecsnode1:~> svc_log -i -f nfs -sr all -sn -sf -n all -start '5 minutes ago' svc_log v0.9.19 (svc_tools v1.1.1) Started 2019-08-14 15:35:57 Running on nodes: <All nodes> Time range: 2019-08-14 15:30:57 - 2019-08-14 15:35:57 Filter string(s): 'nfs' Show filename(s): True Show nodename(s): True Search reclaim logs (if any): False Case insensitive: True 169.254.1.1 dataheadsvc.log 2019-08-14T15:35:05,953 [RpcDispatcherMD-3082827] INFO RpcProgramMountd.java (line 101) MOUNT MNT path: /namespace/nfsbucket Client: /xxx.xxx.xxx 169.254.1.1 dataheadsvc.log 2019-08-14T15:35:05,958 [RpcDispatcherMD-3082827] INFO ExportsService.java (line 98) added key /namespace/nfsbucket/ to the cache 169.254.1.1 dataheadsvc.log 2019-08-14T15:35:05,960 [RpcDispatcherMD-3082827] ERROR RpcProgramMountd.java (line 111) Couldn't locate the exportEntry for the path /namespace/nfsbucket
- Wait ~20 minutes for the conflicting export settings to refresh on the ECS and retry the mount command:
# mount -vv -t nfs -o vers=3,,nolock,sec=sys,proto=tcp <ECS IP>:<Export Path> <local Mount Point>
Example:
[root@client ~]# mount -vv -t nfs -o vers=3,,nolock,sec=sys,proto=tcp xxx.xxx.xxx: /namespace/nfsbucket mnt/test final mount options: 'vers=3,,nolock,sec=sys,proto=tcp' mount.nfs: timeout set for Wed Aug 14 13:55:00 2019 mount.nfs: trying text-based options 'vers=3,nolock,sec=sys,proto=tcp,addr= xxx.xxx.xxx ' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying xxx.xxx.xxx prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=6 mount.nfs: trying xxx.xxx.xxx prog 100005 vers 3 prot TCP port 2049 xxx.xxx.xxx:/namespace/nfsbucket on /mnt/test type nfs (rw,vers=3,,nolock,sec=sys,proto=tcp)
Additional Information
Related NFS KB:
- ECS: How to create a basic NFS export and mount it on a client
- ECS: dataheadsvc log streaming error: NFSv3 procedure LINK not supported in request ReadLinkRequest
- ECS: NFS mounts failing with No such file or directory or ERROR_OBJECT_NOT_FOUND
- ECS: NFS Remote I/O errors; Change of bucket owner for FS enabled bucket may lead to applications/users unable to access NFS files
- ECS: NFS write throws I/O error after a certain amount of data.
- ECS: Using NFS file share from ECS with a VMware NFS datastore
- ECS: Best practices for mounting ECS NFS exports
- ECS: How to mount NFS share on Windows client
- ECS: NFS fails to mount after changing file export settings in the UI
- ECS: Is Oracle WebCenter Content (WCC) compatible with ECS?
Affected Products
ECS ApplianceProducts
ECS Appliance, ECS Appliance Gen 1, ECS Appliance Gen 2, ECS Appliance Gen 3, ECS Appliance Software with Encryption, ECS Appliance Software without EncryptionArticle Properties
Article Number: 000019711
Article Type: How To
Last Modified: 25 Mar 2025
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.