Wed Apr 3 13:25:06.026 2013: mmfsd initializing. {Version: 3.5.0.7 Built: Dec 12 2012 19:00:50} ... Wed Apr 3 13:25:06.731 2013: Pagepool has size 3013632K bytes instead of the requested 29360128K bytes. Wed Apr 3 13:25:07.409 2013: Node 192.168.208.97 (htohru9) is now the Group Leader. Wed Apr 3 13:25:07.411 2013: This node (192.168.208.97 (htohru9)) is now Cluster Manager for htohru9.ltd.sdl. Starting ADSM Space Management daemons Wed Apr 3 13:25:17.907 2013: mmfsd ready Wed Apr 3 13:25:18 JST 2013: mmcommon mmfsup invoked. Parameters: 192.168.208.97 192.168.208.97 all Wed Apr 3 13:25:18 JST 2013: mounting /dev/gpfs Wed Apr 3 13:25:18.179 2013: Command: mount gpfs Wed Apr 3 13:25:18.353 2013: Node 192.168.208.97 (htohru9) appointed as manager for gpfs. Wed Apr 3 13:25:18.798 2013: Node 192.168.208.97 (htohru9) completed take over for gpfs. Wed Apr 3 13:25:19.023 2013: Command: err 0: mount gpfs Wed Apr 3 13:25:19 JST 2013: finished mounting /dev/gpfs 

Depending on the size and complexity of your system configuration, the amount of time to start IBM Spectrum Scale varies. Taking your system configuration into consideration, if you cannot access a file system that is mounted (automatically or by running a mount  command) after a reasonable amount of time, examine the log file for error messages. 

The IBM Spectrum Scale log is a repository of error conditions that were detected on each node, and operational events, such as file system mounts. The IBM Spectrum Scale log is the first place to look when you are attempting to debug abnormal events. Because IBM Spectrum Scale is a cluster file system, events that occur on one node might affect system behavior on other nodes, and all IBM Spectrum Scale logs can have relevant data. 

A common error that might appear when trying to mount GPFS is that it cannot read superblock . Example 10-20 shows the output of the error when trying to mount GPFS. 

[root@ltfsml1 ~]# mmmount gpfs Wed May 24 12:53:59 MST 2017: mmmount: Mounting file systems ... mount: gpfs: can't read superblock mmmount: Command failed. Examine previous error messages to determine cause. 

The cause of this error and failure to mount GPFS is that the GPFS file system had dmapi enabled, but the HSM process has not been started. To get around this error and successfully mount GPFS, issue the systemctl start hsm command, and make sure it is running by issuing systemctl status hsm . After HSM is running, wait for the recall processes to initiate. This process can be viewed by issuing ps -afe | grep dsm . Example 10-21 shows output of starting HSM, checking the status, and mounting GPFS. 

[root@ltfsml1 ~]# systemctl start hsm [root@ltfsml1 ~]# systemctl status hsm ? hsm.service - HSM Service 

