GPFS daemon does not come up

There are several indications that could lead you to the conclusion that the GPFS daemon (mmfsd) does not come up and there are some steps to follow to correct the problem.

Those indications include:
  • The file system has been enabled to mount automatically, but the mount has not completed.
  • You issue a GPFS command and receive the message:
    6027-665
    Failed to connect to file system daemon: Connection refused.
  • The GPFS log does not contain the message:
    6027-300 [N]
    mmfsd ready
  • The GPFS log file contains this error message: 'Error: daemon and kernel extension do not match.' This error indicates that the kernel extension currently loaded in memory and the daemon currently starting have mismatching versions. This situation may arise if a GPFS code update has been applied, and the node has not been rebooted prior to starting GPFS.

    While GPFS scripts attempt to unload the old kernel extension during update and install operations, such attempts may fail if the operating system is still referencing GPFS code and data structures. To recover from this error, ensure that all GPFS file systems are successfully unmounted, and reboot the node. The mmlsmount command can be used to ensure that all file systems are unmounted.