IBM Support

IBM Cloud Pak System or IBM PureApplication System: GPFS client instance update never completes

Troubleshooting


Problem

GPFS client instance update never completes.

Symptom

In the Virtual Application Instances page for an instance, if you click Check for updates in Pattern type and then click Update to update the GPFS pattern version, then the node may get stuck in launch stage resulting in update failure.

Diagnosing The Problem

Check the "gpfs.log" for the following error:
File System FileSystemName_ is only missing on one of the VMs

Resolving The Problem

  1. On the GPFS client node, run the following steps to mount all filesystems that are present in the GPFS server node but not in the client node:
    1. Run the following command to display information about a remote GPFS clusters:   

      su - gpfsprod -c ‘sudo /usr/lpp/mmfs/bin/mmremotecluster show all’

    2. Run the following command to display the information that is associated with a remote GPFS filesystem:

      su - gpfsprod -c ‘sudo /usr/lpp/mmfs/bin/mmremotefs show all’

    3. Run the following command to delete the information for a remote GPFS file system:   

      su - gpfsprod -c ‘sudo /usr/lpp/mmfs/bin/mmremotefs delete <fileSystemName>

    4. Run the following command to define a new remote GPFS file system with enabled automount option:

      su - gpfsprod -c ‘sudo /usr/lpp/mmfs/bin/mmremotefs add <fileSystemName> -f <file System Name>  -C <cluster name> -A yes -T /gpfs/<fileSystemName>’

      Important: Automount option must be enabled otherwise upgrade gets blocked. This upgrade issue occurs because the GPFS waits for a new filesystem to mount. Auto mounting ensures that the manual mounting is not required during the upgrade.
    5. Run the following command to mount a given filesystem:

      su - gpfsprod -c ‘sudo /usr/lpp/mmfs/bin/mmmount /<fileSystemName>-a’

      Here, replace filesystemname with your environment value.

      If this step fails with the following error, then start the GPFS daemon:
      Error:
      Error message: mmmount: Mounting file systems ...
      <Master Boot>:
      mount: unknown filesystem type 'gpfs'
      mmmount: Command failed.

      Use the following command to start the GPFS daemon:

      su - gpfsprod -c 'sudo /usr/lpp/mmfs/bin/mmstartup’

      If you have already created an additional GPFS filesystem after the instance was deployed and filesystem was not set to auto mount, then enable ‘Automount’ parameter using the following command to avoid upgrade failure:

      su - gpfsprod -c 'sudo /usr/lpp/mmfs/bin/mmremotefs update -A yes.

Document Location

Worldwide

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFQSV","label":"IBM Cloud Pak System Software"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"2.2.6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 May 2020

UID

ibm11104639

Page Feedback