File system issues

Remote file systems are defined but not mounted on all nodes

If the RemoteMount controller shows that the target storage cluster file system is established, but the remote file system is not mounted on all the nodes in the ibm-spectrum-scale-core pods, run the following command to mount the file system manually from one of the scale-core pods:

# Replace FILESYSTEM with the name of your filesystem
FILESYSTEM="fs1"
oc exec $(oc get pods -lapp=ibm-spectrum-scale-core -ojsonpath="{.items[0].metadata.name}") -- mmmount $FILESYSTEM -a

Remote file systems unable to mount successfully

Mismatch file system version

On the Filesystem CR, if you see the following event:

Events:
  Type     Reason      Age               From        Message
  ----     ------      ----              ----        -------
  Warning  MountError  6s (x2 over 19s)  Filesystem  Failed to mount filesystem. Filesystem format level on the remote filesystem remote-sample, may be at a higher format level than this version of container native scale.

It means that the remote cluster file system has a newer version than the IBM Storage Scale container native cluster. To fix this issue, upgrade the IBM Storage Scale container native cluster to the same file system level or higher as on the remote cluster.

For more information on supported versions, see Software requirements.