You access the namespace through NFS by mounting a namespace directory on an NFS client. You can mount the namespace as a whole, either root directory (data or metadata), or any specific data directory or metadirectory. Additionally, you can have multiple directories mounted at the same time.
Once mounted, the namespace appears to be part of the local file system, and you can perform any of the operations HCP supports for NFS.
When mounting a namespace, you can use either the domain name of the HCP system or the IP address of a node in the system. Here’s the format for each method:
mount-otcp,vers=3,timeo=600,hard,intr
-t nfsnfs.hcp-domain-name:/fs/tenant-name/namespace-name
[/(data|metadata)[/directory-path]] mount-point-path
mount-otcp,vers=3,timeo=600,hard,intr
-t nfsnode-ip-address:/fs/tenant-name/namespace-name
[/(data|metadata)[/directory-path]] mount-point-path
The parameters shown are recommended but not required.
All parts of the path following the domain name or IP address are case sensitive.
Examples:
mount -o tcp,vers=3,timeo=600,hard,intr -t nfs
nfs.hcp.example.com:/fs/europe/finance HCP-finance
mount -o tcp,vers=3,timeo=600,hard,intr -t nfs
nfs.hcp.example.com:/fs/europe/finance/data datamount
mount -o tcp,vers=3,timeo=600,hard,intr -t nfs
192.168.210.16:/fs/europe/finance/data/presentations/images HCP-images
mount -o tcp,vers=3,timeo=600,hard,intr -t nfs
nfs.hcp.example.com:/fs/europe/finance/metadata metadatamount
![]() |
Note: When mounting the namespace, do not specify the rsize and wsize options. Omitting these options allows HCP to use the optimal values based on system configuration. |
For information on the relative advantages of domain names and IP addresses, see Hostname and IP address considerations.
© 2017 Hitachi Data Systems Corporation. All rights reserved.