ECS: NFS Mount Fails with No Such File or Directory or ERROR_OBJECT_NOT_FOUND

Summary: Network File System (NFS) mounts are failing with "no such file or directory" or "ERROR_OBJECT_NOT_FOUND."

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.
Check out other resources

Symptoms

When mounting an NFS export to a client, the file path shows as not found.

From the NFS client, when attempting to mount the export:
Command: 
# sudo mount -t nfs -o vers=3,sec=sys,proto=tcp <ECS IP>:<Remote Export Path> <Local Mount Point>
Example: 
admin@client~>$ sudo mount -t nfs -o vers=3,sec=sys,proto=tcp x.x.x.x:/NS1/NFS_Bucket/Bos1 /ecs_share
mount.nfs: mounting x.x.x.x:/NS1/NFS_Bucket/Bos1 failed, reason given by server: No such file or directory
Confirmed issue from the ECS logs:
Command: 
# egrep 'ERROR_OBJECT_NOT_FOUND|nfsProcessOperation' /opt/emc/caspian/fabric/agent/services/object/main/log/dataheadsvc.log
Example: 
admin@node1~> egrep 'ERROR_OBJECT_NOT_FOUND|nfsProcessOperation' /opt/emc/caspian/fabric/agent/services/object/main/log/dataheadsvc.log
2016-09-20 18:47:23,666 [RpcDispatcherMD-568497] ERROR RpcProgramMountd.java (line 152) Can't get handle for export: /NS1/NFS_Bucket/Bos1/, error ERROR_OBJECT_NOT_FOUND
2016-09-20 18:47:24,292 [RpcDispatcherMD-568507] WARN FileSystemAccessHelper.java (line 1548) nfsProcessOperation : Object path : Bos1 was not found by method nfsGetOidAndOwnerZone
2016-09-20 18:47:24,293 [RpcDispatcherMD-568507] ERROR RpcProgramMountd.java (line 152) Can't get handle for export: /NS1/NFS_Bucket/Bos1/, error ERROR_OBJECT_NOT_FOUND
2016-09-20 18:47:24,837 [RpcDispatcherMD-568511] WARN FileSystemAccessHelper.java (line 1548) nfsProcessOperation : Object path : Bos1 was not found by method nfsGetOidAndOwnerZone

Cause

This is by design. ECS Administrator Guide outlined:

S3 NFS multiprotocol access to directories and files

ECS supports writing objects using the S3 protocol and accessing them as files using NFS and, conversely, writing files using 
NFS and accessing the files as objects using the S3 protocol. You must understand how directories are managed when you use 
multi-protocol access.

The S3 protocol does not make provision for the creation of folders or directories.

To enable multi-protocol operation, ECS support for the S3 protocol formalizes the use of / and creates directory objects for all 
intermediate paths in an object name. An object named /a/b/c.txt results in the creation of a file object named c.txt and 
directory objects for a and b. The directory objects are not exposed to users through the S3 protocol, and are maintained only 
to provide multi-protocol access and compatibility with file system-based APIs.

This means that /NS1/NFS_Bucket/Bos1 is not a directory as far as NFS is concerned. 

/NS1/NFS_Bucket/Bos1 is considered as directory when there is an object or file under /Bos1/.

Resolution

Create a:

  • Namespace = NS1
  • Bucket = NFS_Bucket
  • Directory = Bos1 
  • WRITE/UPLOAD an Object (Any Object) under Bos1 before trying to mount /NS1/NFS_Bucket/Bos1.

This treats Bos1 as a directory and /NS1/NFS_Bucket/Bos1 can be mounted.

Additional Information

Related NFS articles: The following related articles may require login as a registered Dell Support user to view:

Affected Products

ECS Appliance

Products

ECS Appliance, ECS Appliance Hardware Gen1 U-Series, ECS Appliance Software with Encryption, ECS Appliance Software without Encryption
Article Properties
Article Number: 000052932
Article Type: Solution
Last Modified: 14 Aug 2025
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.