This sub-section describes the AC Warning messages of the GFS Shared File System.
Explanation
Memory allocation failed. The details of the failure are displayed at detail.
Response
Loads on the memory can be the cause of the failure. Consider to expand the actual memory.
Explanation
Loading of the sfcfs module failed. The details of the failure are displayed at detail.
Response
Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
Mounting failed, as an error was detected by specifying mount(2) in the file system. The details of the failure are displayed at detail.
Response
Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
Mounting failed.
Response
Check following points:
If any warning message was output immediately before this message, take an action to deal with the warning message.
Check the network connection state with the node where MDS runs.
Loads on the memory can be the cause of the failure. Consider to expand the actual memory.
If the problem cannot be solved by the above-mentioned procedures, collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
Mounting on the file system (mount_point) failed due to the failure of opening a device (device) which configures the file system.
Response
Check that devices which configure the file system are connected properly.
Explanation
Connection with MDS failed.
Mounting failed when the connection with the primary MDS and secondary MDS on a definition cannot be made.
The details of the failure are displayed at detail.
Response
Check following points:
Check the network connection state with the node where MDS runs.
Check whether the IP address of the node where MDS runs is correctly registered in host database (such as /etc/hosts). For details, see "11.2.2 Registering information in host database."
If the problem cannot be solved after taking the above actions, collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
Mounting is rejected by MDS. The details of the rejection are displayed at detail.
Response
Check following points:
Check /var/log/messages of the node where MDS runs. If there is any warning message output by MDS immediately before this message has output, take an action to deal with the warning message.
Check whether the IP address of this node where MDS runs is correctly registered in host database (such as /etc/hosts). For details, see "11.2.2 Registering information in host database."
When unmounting and mounting are performed in a short time from the blockade of the file system or the node panic, mounting may fail. Spare some time before mounting again.
Explanation
The file system (mount_point) is blockaded, as an illegal message was received from MDS. The details of the blockade are displayed at detail.
Response
Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
Disconnect the connection between the file system (mount_point) and MDS.
Response
None.
Explanation
The file system (mount_point) is blockaded. The details of the blockade are displayed at detail.
Response
Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
There is no more space in the file system (mount_point).
As an ordinary user cannot use the space reserved for a superuser, this message may be output even if there is free space.
Response
Perform any of the following procedures to expand the space of the file system (mount_point):
Expand the file system.
Delete unnecessary files.
Move files to the file system that has enough space.
Use sfcadd(8) to expand the file system.
