Remote file system does not mount
The remote file system mounting failure reasons and the course of action that you can take to resolve the issue.
When a remote file system does not mount, the problem might be with how the file system was defined to both the local and remote nodes, or the communication paths between them. Review the Mounting a file system owned and served by another GPFS cluster topic in the IBM Storage Scale: Administration Guide to ensure that your setup is correct.
These are some of the errors encountered when mounting remote file
systems:
- Remote file system I/O fails with the “Function not implemented” error message when UID mapping is enabled
- Remote file system does not mount due to differing GPFS cluster security configurations
- Cannot resolve contact node address
- The remote cluster name does not match the cluster name supplied by the mmremotecluster command
- Contact nodes down or GPFS down on contact nodes
- GPFS is not running on the local node
- The NSD disk does not have an NSD server specified, and the mounting cluster does not have direct access to the disks
- The cipherList option has not been set properly
- Remote mounts fail with the "permission denied" error message