PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Linux)
Contents Index PreviousNext
Appendix A List of Messages> A.1 AC Messages of the GFS File System

A.1.2 Warning messages

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

 

WARNING: sfcfs: 1001: argument address of mount(2) is invalid value. error occurred in copy_from_user() for mountpoint: error = error

[Explanation]

The mount point that the mount system call passed as an argument is an invalid value.

[Response]

Contact your local Customer Support.

 

WARNING: sfcfs: 1002: argument address of mount(2) is invalid value. error occurred in copy_from_user() for volumeinfo: error = error

[Explanation]

The argument address retaining the volume information that the mount system call passed as an argument is an invalid value.

[Response]

Contact your local Customer Support.

 

WARNING: sfcfs: 1003: argument address of mount(2) is invalid value. error occurred in copy_from_user() for primaryMDS_saddr: error = error

[Explanation]

The argument address retaining the socket address of primary MDS that the mount system call passed as an argument is an invalid value.

[Response]

Contact your local Customer Support.

 

WARNING: sfcfs: 1004: argument address of mount(2) is invalid value. error occurred in copy_from_user() for secondaryMDS_saddr: error = error

[Explanation]

The argument address retaining the socket address of secondary MDS that the mount system call passed as an argument is an invalid value.

[Response]

Contact your local Customer Support.

 

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

[Explanation]

An inconsistency occurred in volid information.

[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]

Opening the volume failed.

[Response]

Check the volume status.

 

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

[Explanation]

Reading the volume information failed.

[Response]

Check the connection status to the disk device.

 

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

[Explanation]

Reading the volume information failed.

[Response]

Check the connection status to the disk device.

 

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 the diagnostic data with pclsnap, and contact your local Customer Support.

 

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 your local Customer Support if it is in the accessible condition.

 

WARNING: sfcfs: 1012: filesystem is in blockade

[ Explanation]

The file system was blockaded.

[ Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support.

 

WARNING: sfcfs: 1013: mountpoint: invalid MOUNT response, so failed to recover: sfi_file = sfi_file: mt_file = mt_file

[ 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: 1014: mountpoint: invalid MOUNT response, so failed to recover: sfi_blksize = 8: mt_blksize = mt_blksize

[ 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: 1015: mountpoint: invalid MOUNT response, so failed to recover: sfi_volinfo_len = sfi_volinfo_len: mt_volinfo_len = mt_volinfo_len

[ 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: 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

[ 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: 1018: mountpoint: received header message is bigger than Request-reply message came from MDS: received size = received size: Request-reply message = Request-reply message

[ 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: 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

[ Explanation]

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

[ Response]

Check the network, node, and IP address settings.

 

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 system is blockaded because there is no heartbeat Response for the host name (hostname) of the file system (mountpoint).

[ 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 meta-data server, 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

[ Explanation]

Memory allocation failed.

[ Response]

Increase the memory or the swap space.

 

WARNING: sfcfs: 1029: mountpoint: cannot allocate memory space for Node

[ Explanation]

Memory allocation failed.

[ Response]

Increase the memory or the swap space.

 

WARNING: sfcfs: 1030: mountpoint: cannot allocate memory space. so failed to allocate Call

[ Explanation]

Memory allocation failed.

[ Response]

Increase the memory or the swap space.

 

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 which was previously mounted.

[ Response]

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

Contents Index PreviousNext
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004