A.1.2 Warning messages

This sub-section describes the AC Warning messages of the GFS Shared File System.

WARNING: sfcfs: 1001: argument address of mount(2) is invalid value.  error occurred in copy_from_user() for mountpoint: error = error
WARNING: sfcfs: 1002: argument address of mount(2) is invalid value.  error occurred in copy_from_user() for volumuinfo: error = error
WARNING: sfcfs: 1003: argument address of mount(2) is invalid value.  error occurred in copy_from_user() for primaryMDS_saddr: error = error
WARNING: sfcfs: 1004: argument address of mount(2) is invalid value.  error occurred in copy_from_user() for secondaryMDS_saddr: error = error

Explanation

The address from mount(2) is invalid.

Response

Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.

WARNING: sfcfs: 1005: mountpoint: volume id from MDS is invalid value: volid = volid

Explanation

Volume information is inconsistent.

Response

Unmount the relevant file system from all of the nodes, and check the file system configuration and the network, node, and IP address settings.

WARNING: sfcfs: 1006: mountpoint: volume id from MDS is invalid value. so volume is busy: volid = volid

Explanation

The specified volume has been used by another FS or mounted in a different mode.

Response

Unmount the relevant file system from all of the nodes, and check the file system configuration and the network, node, and IP address settings.

WARNING: sfcfs: 1007: mountpoint: failed to open volumes requested from MDS, no volume to open

Explanation

The partition that configures the file system cannot be opened.

Response

Check the state of the GDS volume.

WARNING: sfcfs: 1008: failed to read superblock information from disk associated device
WARNING: sfcfs: 1009: failed to read volume information from disk associated device

Explanation

Reading the volume failed.

Response

Check the volume status.

WARNING: sfcfs: 1010: failed to get volume information, when try to get extents: volid = volid

Explanation

An inconsistency occurred in the data volume information management.

Response

Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.

WARNING: sfcfs: 1011: failed to access to volume information, when try to get extents: volid = volid

Explanation

The data volume is not accessible.

Response

Check the volume status, and contact field engineers if it is in the accessible condition.

WARNING: sfcfs: 1012: filesystem is in blockade

Explanation

The file system was blockaded.

Response

Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.

WARNING: sfcfs: 1013: mountpoint: invalid MOUNT response, so failed to recover: sfi_file = sfi_file: mt_file = mt_file
WARNING: sfcfs: 1014: mountpoint: invalid MOUNT response, so failed to recover: sfi_blksize = 8: mt_blksize = mt_blksize
WARNING: sfcfs: 1015: mountpoint: invalid MOUNT response, so failed to recover: sfi_volinfo_len = sfi_volinfo_len: mt_volinfo_len = mt_volinfo_len
WARNING: sfcfs: 1016: mountpoint: invalid MOUNT response, so failed to recover: sfi_vli_blocks = sfi_vli_blocks: mt_volinfo.mt_volinfo_val[num].vli_blocks=mt_volinfo.mt_volinfo_val[num].vli_blocks

Explanation

The call for MDS failure recovery of the file system (mountpoint) resulted in an error. The file system (mountpoint) becomes no longer available from the node.

Response

Unmount the relevant file system, and check the file system configuration and the network, node, and IP address settings.

WARNING: sfcfs: 1017: mountpoint: received header message is short: received size = received size: required size = required size
WARNING: sfcfs: 1018: mountpoint: received header message is bigger than Request-reply message came from MDS: received size = received size: Request-reply message = Request-reply message
WARNING: sfcfs: 1019: mountpoint: received body message is short: received size = received size: required size = required size

Explanation

An illegal message was received in communication with MDS of the file system (mountpoint). The file system becomes no operational.

Response

Unmount the relevant file system from the node on which the message was output, and check the network, node, and IP address settings.

WARNING: sfcfs: 1020: mountpoint: failed to send request to MDS: error = error: procedure_num = procedure_num

Explanation

An error occurred in communication with MDS of the file system (mountpoint).

Response

The operation can be continued when no other error message is output.

WARNING: sfcfs: 1021: mountpoint: failed to connect to PrimaryMDS: error=error IP=ipaddress

Explanation

Connecting to primary MDS (ipaddress) failed. Mounting the file system (mountpoint) fails.

Response

Check following points:

Check the network connection state with the node where the primary MDS runs.
Check whether the IP address of the node where the primary 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.

WARNING: sfcfs: 1022: mountpoint: failed to connect to SecondaryMDS: error = error

Explanation

Connecting to secondary MDS failed. Mounting the file system (mountpoint) fails.

Response

Check the network, node, and IP address settings.

WARNING: sfcfs: 1023: mountpoint: no response of heartbeat from Server MDS, so blockade

Explanation

The file system (mountpoint) is blockaded because heartbeat monitoring to the primary MDS is disconnected.

Response

Check the file system whether it is in continuous use. If it is no longer in continuous use, check and restore the network connection and the MDS, and then mount the file system again.

WARNING: sfcfs: 1024: mountpoint: cannot allocate memory space. so failed to create node for mountpoint

Explanation

Memory allocation failed.

Response

Increase the memory or the swap space.

WARNING: sfcfs: 1025: mountpoint: cannot allocate memory space. so failed to Spawn Xagent to receive Request from MDS

Explanation

Generating Xagent failed on mounting the file system (mountpoint).

Response

Increase the memory or the swap space.

WARNING: sfcfs: 1026: mountpoint: cannot allocate memory space. so failed to run Xagent

Explanation

Activation of the daemon to control multiple hosts to the file system (mountpoint) failed. The mounting fails.

Response

Check the memory and the swap space whether they are sufficient by looking up the console message and so on. If insufficient, increase the size, and then mount the file system again.

WARNING: sfcfs: 1027: mountpoint: cannot allocate memory space. so failed to run Clientds

Explanation

Activation of the daemon to control multiple hosts to the file system (mountpoint) failed. The mounting fails.

Response

Check the memory and the swap space whether they are sufficient by looking up the console message and so on. If insufficient, increase the size, and then mount the file system again.

WARNING: sfcfs: 1028: mountpoint: cannot allocate memory space for pagecache
WARNING: sfcfs: 1029: mountpoint: cannot allocate memory space for Node
WARNING: sfcfs: 1030: mountpoint: cannot allocate memory space. so failed to allocate Call
WARNING: sfcfs: 1031: cannot allocate memory space for xdr

Explanation

Memory allocation failed.

Response

Increase the memory or the swap space.

WARNING: sfcfs: 1032: mountpoint: mount for fsid=fsid was failed, because MDS was releasing the node information which was previously mounted.

Explanation

Mount processing of the file system (mountpoint) fails, because MDS was releasing the node information that was previously mounted.

Response

Mount the file system (mountpoint) again after some interval.

WARNING: sfcfs: 1033: Not enough memory: detail

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.

WARNING: sfcfs: 1034: Failed to add module: detail

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.

WARNING: sfcfs: 1035: Invalid mount argument: detail

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.

WARNING: sfcfs: 1036: Mount failed: errcode=errcode

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.

WARNING: sfcfs: 1037: mount_point: Failed to open device=device errcode=errcode

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.

WARNING: sfcfs: 1038: mount_point: Cannot connect MDS: detail

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.

WARNING: sfcfs: 1039: mount_point: MDS reject mount: detail

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.

WARNING: sfcfs: 1040: mount_point: Protocol error: detail

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.

WARNING: sfcfs: 1041: mount_point: Disconnect MDS

Explanation

Disconnect the connection between the file system (mount_point) and MDS.

Response

None.

WARNING: sfcfs: 1042: mount_point: Blockade: detail

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.

WARNING: sfcfs: 1043: mount_point: File system full

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.