PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)

E.1.2 Warning messages

This subsection explains the AC (kernel) warning message of the GFS Shared File System.

E.1.2.1 WARNING: sfcfs:0005: mount_point: daemon create failed

[Explanation]

A daemon could not be created during an attempt to mount a file system (mount_point.)

[Action]

The memory load is thought as a cause. Please examine the increase of a real memory.

E.1.2.2 WARNING: sfcfs:0006: mount_point: too many file systems.

[Explanation]

The file system (mount_point) management table is full.

[Action]

Unmount unnecessary GFS Shared File Systems for the related node.

E.1.2.3 WARNING: sfcfs:0070: mount_point: super block read error. dev = dnum

[Explanation]

Failed to read a super block on the device (device number is dnum) when mounting the file system (mount_point.) Mount processing fails.

[Action]

Respond according to Appendix G.2.1, "Action for I/O errors," in this manual.

E.1.2.4 WARNING: sfcfs:0074:mount_point: primary and secondary super blocks are different. dev = dnum

[Explanation]

An inconsistency was detected between the contents of the primary super block and the contents of the secondary super block on the device (device number is dnum.) Mounting mount_point fails.

[Action]

Display partition information by fstyp_sfcfs(1M) with -v option, and confirm to the file system composition errorless it. Check whether the configuration of the specified file system is normal. If it is abnormal, make the file system again. If it is normal, execute the sfcadm(1M) with no option to set up the information on file system configuration again, then retry mounting after recover the file system with fsck_sfcfs(1M).

E.1.2.5 WARNING: sfcfs:0075: mount_point: partition configuration read error. dev = dnum

[Explanation]

Failed to read partition configuration data on the device (device number is dnum) when mounting the file system (mount_point.) Mount processing fails.

[Action]

Respond according to Appendix G.2.1, "Action for I/O errors," in this manual.

E.1.2.6 WARNING: sfcfs:0078: mount_point: primary and secondary partition configuration are different. dev = dnum

[Explanation]

An inconsistency was detected between the primary partition configuration data and secondary partition configuration data on the device (device number is dnum.) Mounting mount_point fails.

[Action]

Display partition information by fstyp_sfcfs(1M) with -v option, and confirm to the file system composition errorless it. Check whether the configuration of the specified file system is normal. If it is abnormal, make the file system again. If it is normal, execute the sfcadm(1M) with no option to set up the information on file system configuration again, then retry mounting after recover the file system with fsck_sfcfs(1M).

E.1.2.7 WARNING: sfcfs:0080: mount_point: node information not found for node

[Explanation]

Information for the indicated node was not found in the file system (mount_point.)

[Action]

Register correct node information using sfcnode(1M).

E.1.2.8 WARNING: sfcfs:0081: mount_point: super blocks differ. dev dnum to dnum

[Explanation]

An inconsistency was found in the super block information in the indicated file system (mount_point) in a multiple partition configuration. Mounting fails.

[Action]

Display partition information by fstyp_sfcfs(1M) with -v option, and confirm to the file system composition errorless it. Check whether the configuration of the specified file system is normal. If it is abnormal, make the file system again. If it is normal, execute the sfcadm(1M) with no option to set up the information on file system configuration again, then retry mounting after recover the file system with fsck_sfcfs(1M).

E.1.2.9 WARNING: sfcfs:0090: mount_point: reply timeout (proc=pnum, xid=xid)

[Explanation]

A reply time-out occurred during communication with the meta-data server. The file system (mount_point) cannot be used.

[Action]

Unmounting that includes the file system of the node from which the message was issued. Determine the cause of the communication time-out. When an unmount processing fails, restart the node.

E.1.2.10 WARNING: sfcfs:0091: mount_point: connection failed to ip=iaddr, port=pnum, err=ecode

E.1.2.11 WARNING: sfcfs:0092: mount_point: connection failed to ip=iaddr, port=pnum, err=ecode

[Explanation]

A TCP/IP connection could not be established with the indicated IP address (iaddr) and indicated port number (pnum.) Mounting the file system (mount_point) fails.

[Action]

Check the network, node, and IP address settings.

E.1.2.12 WARNING: sfcfs:0093: mount_point: server not found

[Explanation]

The server to be connected could not be found during meta-data server failure recovery. The file system (mount_point) cannot be used.

[Action]

Unmount the file system of the node from which the message was issued. The file system management data may be illegal. Check whether configuration data is valid using sfcinfo(1M).

E.1.2.13 WARNING: sfcfs:0094: mount_point: server not specified

[Explanation]

No meta-data server was specified in a mount system call. Mounting the file system (mount_point) fails.

[Action]

Contact local Customer Support.

E.1.2.14 WARNING: sfcfs:0095: mount_point: protocol error (msg type mtype)

E.1.2.15 WARNING: sfcfs:0096: mount_point: protocol error (xid == 0)

E.1.2.16 WARNING: sfcfs:0097: mount_point: protocol error (not found corresponding request. list=rlen, xid=xid)

E.1.2.17 WARNING: sfcfs:0098: mount_point: protocol error (reply stat rstat)

E.1.2.18 WARNING: sfcfs:0099: mount_point: protocol error (accept stat astat)

[Explanation]

An illegal message was received during communication with the meta-data server. The file system (mount_point) cannot be used.

[Action]

Unmount the file system of the node from which the message was issued. Check the network, node, and IP address settings.

E.1.2.19 WARNING: sfcfs:0100: mount_point: no response from server

[Explanation]

Communication with the meta-data server was lost. The file system (mount_point) cannot be used.

[Action]

Unmount the file system of the node from which the message was issued. Check the network, node, and IP address settings.

E.1.2.20 WARNING: sfcfs:0101: mount_point: message send failed. proc=pnum, err=ecode

[Explanation]

An error occurred during communication with the meta-data server of mount_point.

[Action]

Operation can be continued if there's no other error message.

E.1.2.21 WARNING: sfcfs:0103: mount_point: rpc daemon not exists (proc=pnum)

[Explanation]

Communication failed because a communication request was issued when no communication daemon for the indicated file system (mount_point) existed.

[Action]

Processing is not affected.

E.1.2.22 WARNING: sfcfs:0104: mount_point: unknown request pnum

[Explanation]

The indicated file system (mount_point) received an unexpected communication request.

[Action]

Processing is not affected.

E.1.2.23 WARNING: sfcfs:0105: mount_point: rpc daemon receive failed. err = ecode

[Explanation]

A receive error occurred on the communication path to the meta-data server of the indicated file system (mount_point.) The file system cannot be used.

[Action]

Unmount the file system of the node from which the message was issued. Check the network, node, and IP address settings.

E.1.2.24 WARNING: sfcfs:0106: mount_point: No messages are available to be received

[Explanation]

A receive error occurred on the communication path to the meta-data server of the indicated file system (mount_point.)

[Action]

The GFS Shared File System attempts automatic recovery. Unless another error message is issued, the file system can be used the way it is.

E.1.2.25 WARNING: sfcfs:0107: mount_point: request timeout (proc=pnum)

[Explanation]

An error occurred during communication with the meta-data server of the indicated file system (mount_point.)

[Action]

The GFS Shared File System attempts automatic recovery. Unless another error message is issued, the file system can be used the way it is.

E.1.2.26 WARNING: sfcfs:0108: mount_point: mount failed. (pname procedure failed) sfcfs_error = ecode

[Explanation]

An error occurred during communication with MDS of the file system (mount_point.) Mount processing fails.

[Action]

If MDS has outputted the warning message to /var/adm/messages of MDS node just before this message, apply the countermeasures described in that message.

Unmount the file system at the node at which this message appeared. Confirm the setting of the network, node, and IP address.

E.1.2.27 WARNING: sfcfs:0109: mount_point: UNMOUNT procedure failed. sfcfs_error = err

[Explanation]

An error occurred during communication with MDS of the file system (mount_point.) No process is affected.

[Action]

Processing is not affected.

E.1.2.28 WARNING: sfcfs:0110: invalid parameter length len

[Explanation]

The length (len) of a parameter in a mount system call is invalid. Mounting fails.

[Action]

Contact local Customer Support.

E.1.2.29 WARNING: sfcfs:0111: mount_point: invalid recover

[Explanation]

A system call for meta-data server failure recovery contains an invalid parameter. The file system (mount_point) cannot be used.

[Action]

Unmount the indicated file system, and then mount it again.

E.1.2.30 WARNING: sfcfs:0112: mount_point: recover failed for secondary. (error in rpcd ecode)

[Explanation]

An error occurred in a system call for meta-data server failure recovery of mount_point.

[Action]

This message indicates a failure in secondary server recovery processing. There is no problem in using the file system. The file system can be used the way it is.

E.1.2.31 WARNING: sfcfs:0113: mount_point: recover failed for primary. (error in rpcd ecode)

[Explanation]

An error occurred in a system call for meta-data server failure recovery of mount_point.

[Action]

Recovery processing of the primary meta-data server failed. The GFS Shared File System attempts automatic recovery. Unless another error occurs, the file system can be used the way it is.

E.1.2.32 WARNING: sfcfs:0114: mount_point: recover failed. (nprocs = nprocs)

E.1.2.33 WARNING: sfcfs:0115: mount_point: recover failed. (MOUNT procedure) err=ecode

[Explanation]

An error occurred in a system call for meta-data server failure recovery of the file system (mount_point.)

[Action]

The GFS Shared File System attempts automatic recovery. Unless another error message is issued, the file system can be used the way it is.

E.1.2.34 WARNING: sfcfs:0116: mount_point: recover failed. (invalid MOUNT response, sfi_file: file_handle, mt_file: file_handle)

E.1.2.35 WARNING: sfcfs:0117: mount_point: recover failed. (invalid MOUNT response, sfi_blksize = blksize, mt_blksize = blksize)

E.1.2.36 WARNING: sfcfs:0118: mount_point: recover failed. (invalid MOUNT response, sfi_tsize = tsize, mt_tsize = tsize)

E.1.2.37 WARNING: sfcfs:0119: mount_point: recover failed. (invalid MOUNT response, sfi_flags = flags, mt_flags = flags)

E.1.2.38 WARNING: sfcfs:0120: mount_point: recover failed. (invalid MOUNT response, sfi_extpower = extpower, mt_extpower = extpower)

E.1.2.39 WARNING: sfcfs:0121: mount_point: recover failed. (invalid MOUNT response, sfi_extlevel = extlevel, mt_extlevel = extlevel)

E.1.2.40 WARNING: sfcfs:0122: mount_point: recover failed. (invalid MOUNT response, sfi_volinfo_len = len, mt_volinfo_len = len)

E.1.2.41 WARNING: sfcfs:0123: mount_point: recover failed. (invalid MOUNT response, volinfo[volid] mismatch)

E.1.2.42 WARNING: sfcfs:0124: mount_point: recover failed. (BARSYNC(flags) time-out)

E.1.2.43 WARNING: sfcfs:0125: mount_point: recover failed. (bs_cmnd(flags) != expected_flags)

E.1.2.44 WARNING: sfcfs:0126: mount_point: recover failed. (resend error ecode)

E.1.2.45 WARNING: sfcfs:0127: mount_point: recover failed. (resend timeout, rest=nprocs)

E.1.2.46 WARNING: sfcfs:0128: mount_point: recover failed. (resend error ecode)

E.1.2.47 WARNING: sfcfs:0129: mount_point: recover failed. (UMOUNT procedure) err= ecode

E.1.2.48 WARNING: sfcfs:0130: mount_point: recover failed. (RECOVER procedure) ino=inum, err=ecode

E.1.2.49 WARNING: sfcfs:0131: mount_point: recover failed. (RECOVER procedure) ino=inum, sfcfs_err=ecode

E.1.2.50 WARNING: sfcfs:0132: mount_point: recover failed. (resend error ecode)

E.1.2.51 WARNING: sfcfs:0133: mount_point: recover failed. (resend timeout, rest=nprocs)

E.1.2.52 WARNING: sfcfs:0134: mount_point: recover failed. (BARSYNC(flags) procedure) err= ecode

E.1.2.53 WARNING: sfcfs:0135: mount_point: recover failed. (FSCTL(flags) procedure) err= ecode

[Explanation]

An error occurred in a system call for meta-data server failure recovery. The indicated file system (mount_point) cannot be used from the related node.

[Action]

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

E.1.2.54 WARNING: sfcfs:0136: mount_point: recover failed. drvname is not found. (major= 0xnum)

[Explanation]

An inconsistency was detected during a recovery processing on the file system (mount_point.) The inconsistency will be resolved and the processing will continue.

[Action]

No response is required.

E.1.2.55 WARNING: sfcfs:0139: mount_point: volinfo is different. (invalid VOLINFO, volinfo[num] mismatch)

E.1.2.56 WARNING: sfcfs:0139: mount_point: volinfo is different. (invalid VOLINFO, sfi_volinfo_len = num, vi_volinfo_len = num))

E.1.2.57 WARNING: sfcfs:0139: mount_point: volinfo is different. (invalid VOLINFO, volid = num, sfi_volinfo_val[num].vli_volid = num)

[Explanation]

Detected a mismatch in control table volinfo. An error preventing the continuation of processing is detected, therefore, the file system (mount_point) is shut down.

[Action]

Unmount the file system in all nodes. Confirm the setting of the file system configuration, network, node, and IP address.

E.1.2.58 WARNING: sfcfs:0140: mount_point: cannot access: too many I/O errors. dev = dnum

[Explanation]

The file system (mount_point) is shut down because of a super block read error on the device (device number is dnum.) Access to the file system will cause an error return.

[Action]

Respond according to Appendix G.2.1, "Action for I/O errors," in this manual.

E.1.2.59 WARNING: sfcfs:0200: mount_point: daemon create failed

E.1.2.60 WARNING: sfcfs:0201: mount_point: daemon create failed

[Explanation]

Daemon creation during mounting of the file system (mount_point) is incomplete.

[Action]

The memory load is thought as a cause. Please examine the increase of a real memory.

E.1.2.61 WARNING: sfcfs:0204: mount_point: I=inum mds down rreload garbage collect

E.1.2.62 WARNING: sfcfs:0205: mount_point: I=inum mds down rarchive garbage collect

[Explanation]

Error occurs in MDS communications for the file (inum) in the file system (mount_point.)

[Action]

Operation can be continued if there's no other error message.

E.1.2.63 WARNING: sfcfs:0221: mount_point: recover failed. sfcfs_hsm_recover error=ecode

[Explanation]

An error has occurred in a system call for MDS down recovery. The file system (mount_point) cannot be used from the node.

[Action]

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

E.1.2.64 WARNING: sfcfs:0250: mount_point: mpathd daemon create failed

[Explanation]

Activation of the daemon for the file system (mount_point) to control multiple hosts is incomplete. Mounting is going to fail.

[Action]

The memory load is thought as a cause. Please examine the increase of a real memory.

E.1.2.65 WARNING: sfcfs:0252: address family not specified

[Explanation]

Invalid network information has been specified. Mounting is going to fail.

[Action]

Check the network settings.

E.1.2.66 WARNING: sfcfs:0253: address family (0xnum) not supported

[Explanation]

Address family of the specified network is not supported. Mounting is going to fail.

[Action]

Change the network settings to use applicable network address family.

E.1.2.67 WARNING: sfcfs:0254: unknown address family (0xnum)

[Explanation]

Address family of the specified network is not supported. Mounting is going to fail.

[Action]

Change the network settings to use the correct network address family.

E.1.2.68 WARNING: sfcfs:0255: server address check failed

[Explanation]

The self-node TCP/IP setup data cannot be obtained. Mounting is going to fail.

[Action]

Mount the file system again.

E.1.2.69 WARNING: sfcfs:0256: mount_point: no mpath heartbeat response from server MDS=(addr=hostname, port=num)

[Explanation]

There's no heartbeat response from MDS on hostname.

[Action]

In the node that output messages, check whether the file system is capable of continuing operation. When it is not capable of continuing, check the network connection and meta data server conditions. After restoring, mount the file system in the node that output messages again.

E.1.2.70 WARNING: sfcfs:0259: mount_point: mpath connection wasn't established MDS=(addr=hostname, port=num), error=error

[Explanation]

Re-connection to the MDS on hostname is incomplete.

[Action]

In the node that output messages, check whether the file system is capable of continuing operation. When it is not capable of continuing, check the network connection and meta data server conditions. After restoring, restart the file system in the node that output messages again.

E.1.2.71 WARNING: sfcfs:0260: mount_point: mpath connect was failed MDS=(addr=hostname, port=num), error=error

[Explanation]

Connection to the MDS on hostname is incomplete.

[Action]

Check the network connection and meta data server conditions. After restoring, mount the file system in the node that output messages again.

E.1.2.72 WARNING: sfcfs:0261: mount_point: mpath connection was broken MDS=(addr=hostname, port=num), error=error

[Explanation]

There's no heartbeat response from the MDS on hostname.

[Action]

In the node that output messages, check whether the file system is capable of continuing operation. When it is not capable of continuing, check the network connection and meta data server conditions. After restoring, mount the file system in the node that output messages again.

E.1.2.73 WARNING: sfcfs:0262: mount_point: bad mpath seqno ac(num1) mds(num2)

[Explanation]

An inconsistency has arisen in the sequence number management between MDS and AC.

[Action]

In the node that output messages, check whether the file system is capable of continuing operation. When it is not capable of continuing, check the network connection and meta data server conditions. After restoring, mount the file system in the node that output messages again.

E.1.2.74 WARNING: sfcfs:0263: invalid version number version

[Explanation]

Invalid version information specified for argument of mount system call. An inconsistency occurs between the file system management commands and AC versions. Mounting is going to fail.

[Action]

Check that a package is applied properly to all the nodes.

E.1.2.75 WARNING: sfcfs:0264: mount_point: switchover failed. error=ecode

[Explanation]

Host exchange in the multiple LAN function of the file system (mount_point) is incomplete.

[Action]

In the node that output messages, check whether the file system is capable of continuing operation. When it is not capable of continuing, check the network connection and meta data server conditions. After restoring, mount the file system in the node that output messages again.E.1.3