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

E.3.3 Warning messages

This section explains the warning message of each daemon of the GFS Shared File System.

E.3.3.1 MDS (sfcfsmg) daemon

E.3.3.1.1 WARNING: sfcfs_mds:0005: mount_point: daemon create failed

[Explanation]

A daemon could not be created when mount the file system (mount_point.) Memory of system is insufficient.

[Action]

Increase the swap space or the real memory.

E.3.3.1.2 WARNING: sfcfs_mds:0006: mount_point: too many file systems.

[Explanation]

The file system management table is full (mount_point.)

[Action]

In the all nodes, unmount unnecessary GFS Shared File Systems.

E.3.3.1.3 WARNING: sfcfs_mds:0021: can't allocate memory in primary MDS for mount_point

[Explanation]

Memory could not be allocated on the primary meta-data server for the file system (mount_point.) Memory of system is insufficient.

[Action]

Increase the swap space or the real memory.

E.3.3.1.4 WARNING: sfcfs_mds:0022: can't allocate memory in secondary MDS for mount_point

[Explanation]

Memory could not be allocated on the secondary meta-data server for the file system (mount_point.) Memory of system is insufficient.

[Action]

Increase the swap space or the real memory.

E.3.3.1.5 WARNING: sfcfs_mds:0022: mount_point: bad dir ino inum at offset off : info

[Explanation]

An error was detected in a directory entry of the file system (mount_point.)

[Action]

Unmount the file system in all node, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.6 WARNING: sfcfs_mds:0023: can't allocate memory in taking over MDS for mount_point

E.3.3.1.7 WARNING: sfcfs_mds:0023: can't allocate memory in taking over MDS for mount_point, errcode=ecode

[Explanation]

Memory could not be allocated during meta-data server for the file system (mount_point) switch processing. Memory of system is insufficient.

[Action]

Increase the swap space or the real memory.

E.3.3.1.8 WARNING: sfcfs_mds:0023: mount_point: target directory link count < 2 ino = inum

[Explanation]

An error was detected in directory management data of the file system (mount_point.)

[Action]

Unmount the file system in all node, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.9 WARNING: sfcfs_mds:0024: can't allocate memory for buf_name (size size, errcode ecode) in logreplay: mount_point

[Explanation]

Memory could not be allocated during update log replay for the file system (mount_point.) Memory of system is insufficient.

[Action]

Increase the swap space or the real memory.

E.3.3.1.10 WARNING: sfcfs_mds:0024: mount_point: invalid offset off ino = inum

[Explanation]

An error was detected in a directory entry of the file system (mount_point.)

[Action]

Unmount the file system in all node, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.11 WARNING: sfcfs_mds:0027: mount_point: bad dir, ino = inum

[Explanation]

An error was detected in an entry in a directory of the file system (mount_point.)

[Action]

Unmount the file system, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.12 WARNING: sfcfs_mds:0030: mount_point: meta data read error. type = number dev = dnum block = block_num size = size

E.3.3.1.13 WARNING: sfcfs_mds:0031: mount_point: meta data read error. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to read the meta-data area of the file system (mount_point) from a device (device number is dnum.)

[Action]

Take action according to the instructions in Appendix G.2.1, "Action for I/O errors."

E.3.3.1.14 WARNING: sfcfs_mds:0032: mount_point: bitmap read error. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to read the bitmap area of the file system (mount_point) from a device (device number is dnum.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.15 WARNING: sfcfs_mds:0033: mount_point: bitmap read error. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to read the bitmap area of the file system (mount_point) from a device (device number is dnum.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.16 WARNING: sfcfs_mds:0034: mount_point: bitmap read error. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to read the bitmap area of the file system (mount_point) from a device (device number is dnum.) The released area was made invalid.

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.17 WARNING: sfcfs_mds:0035: mount_point: bitmap write error. information was lost. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write to the bitmap area of the file system (mount_point) on a device (device number is dnum.) Part of the file system (mount_point) information was lost.

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.18 WARNING: sfcfs_mds:0036: mount_point: bitmap write error. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write to the bitmap area of the file system (mount_point) on a device (device number is dnum.)

[Action]

Unless message sfcfs_mds:0035 or sfcfs_mds:0039 is issued, recovery by retry processing was successful, so no response is required.

E.3.3.1.19 WARNING: sfcfs_mds:0037: mount_point: meta data write error. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write to the meta-data area of the file system (mount_point) on the device (device number is dnum.)

[Action]

Unless message sfcfs_mds:0040 is issued, recovery by retry processing was successful, so no response is required.

E.3.3.1.20 WARNING: sfcfs_mds:0038: mount_point: fail to update super block at first time. dev = dnum block = block_num size = size

[Explanation]

Super blocks of the file system (mount_point) could not be updated during mount processing. Mounting fails.

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.21 WARNING: sfcfs_mds:0039: mount_point: bitmap write error. information was lost. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write to the bitmap area of the file system (mount_point) on a device (device number is dnum.) Part of the file system (mount_point) information was lost.

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.22 WARNING: sfcfs_mds:0040: mount_point: meta data write error. information was lost. type = number dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write to the meta-data area of the file system (mount_point) on a device (device number is dnum.) Part of the file system (mount_point) information was lost.

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.23 WARNING: sfcfs_mds:0042: mount_point: LOG daemon is dead. dev = dnum

[Explanation]

The log daemon stopped processing because it could not recover from a failure to write to the update log area of the file system (mount_point) on a device (device number is dnum.)

[Action]

Because of an I/O error, the update log daemon was not able to operate and terminated. The file system access performance is degraded because operation is continued without the update log available. Back up the file system, and take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.24 WARNING: sfcfs_mds:0043: mount_point: super block write error. dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write a super block of the file system (mount_point) to a device (device number is dnum.)

[Action]

Unless message sfcfs_mds:0044 is issued, recovery was performed by retry processing, so no response is required.

E.3.3.1.25 WARNING: sfcfs_mds:0044: mount_point: super block write error. information was lost. dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write a super block of the file system (mount_point) to a device (device number is dnum.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.26 WARNING: sfcfs_mds:0046: mount_point: cannot access: too many I/O errors. dev = dnum

[Explanation]

A file system was shut down because of a super block write error. If this file system (mount_point) is accessed subsequently, an error is returned.

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.27 WARNING: sfcfs_mds:0063: mount_point: cannot delete extent. ino = inum len = len width = width length = len

[Explanation]

An error in extent-based management of the file (inum) on the file system (mount_point) was detected.

[Action]

Unmount the file system in all nodes, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.28 WARNING: sfcfs_mds:0064: mount_point: no extent exists. ino = inum osize = len len = len

[Explanation]

An error in extent-based management of the file (inum) on the file system (mount_point) was detected.

[Action]

Unmount the file system, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.29 WARNING: sfcfs_mds:0065: mount_point: cannot delete extent of directory. ino = inum len = len width = width length = len

[Explanation]

An error in extent-based management of the file (inum) on the file system (mount_point) was detected.

[Action]

In all the nodes, unmount the indicated file system, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.30 WARNING: sfcfs_mds:0070: mount_point: super block read error. dev = dnum

[Explanation]

A super block could not be read from device (device number is dnum) when the mount the file system (mount_point) started.

[Action]

Unmount the indicated file system, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.31 WARNING: sfcfs_mds: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.)

[Action]

Check whether the specified file system configuration is normal. If it is normal, set the file system configuration data again using sfcadm(1M), perform file system recovery using fsck_sfcfs(1M), and mount file system again.

E.3.3.1.32 WARNING: sfcfs_mds:0075: mount_point: partition configuration read error. dev = dnum

[Explanation]

Partition configuration data could not be read when mount the file system (mount_point) started.

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.33 WARNING: sfcfs_mds:0078: 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.)

[Action]

In the case that the file system is restored and not adjusted file system configuration by sfcadm(1M), set the file system configuration data again using sfcadm(1M), perform file system recovery using fsck_sfcfs(1M), and mount file system again.

E.3.3.1.34 WARNING: sfcfs_mds:0080: mount_point: node information not found for node

[Explanation]

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

[Action]

• If you performed an operation according to the following procedure, mount the file system in a shared node, which was started during the backup, of the target file system:
  1. When some of the shared nodes of the target file system were stopped, you used sfcproxyop backup or part to create a backup, and:
  2. You used sfcproxyop mount to mount the backup destination.
• In all other cases, register correct node information using sfcnode(1M).

E.3.3.1.35 WARNING: sfcfs_mds: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.

[Action]

Check whether the specified file system configuration is normal. If it is normal, set the file system configuration data again using sfcadm(1M), perform file system recovery using fsck_sfcfs(1M), and mount the file system again.

E.3.3.1.36 WARNING: sfcfs_mds:0082: mount_point: partition configuration differ. dev dnum to dev devlist_num

[Explanation]

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

[Action]

In the case that the file system is restored and not adjusted file system configuration by sfcadm(1M), set the file system configuration data again using sfcadm(1M), perform file system recovery using fsck_sfcfs(1M), and mount the file system again.

E.3.3.1.37 WARNING: sfcfs_mds:0112: mmap can't access between other nodes. mnt= mount_point, ino=inum, nodename(node1, node2), mode(mode1, mode2)

[Explanation]

open(2) and mmap(2) that cannot be maintain the consistency of the data was issued to the same file.

[Action]

Please wait for the termination of the process running on the "node1" indicated this message, and execute again.

To determine the process using the file (inum), act according to the following sequence:

1. determine the filename of the i-number, using find(1) with -inum option.
2. determine the process ID using the filename, using fuser(1M).
3. determine the command name of the process ID, using ps(1).

E.3.3.1.38 WARNING: sfcfs_mds:0131: mount_point: super block write error. dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write a super block to a device (device number is dnum.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.39 WARNING: sfcfs_mds:0133: mount_point: volume information write error. dev = dnum block = block_num size = size

[Explanation]

An error occurred during an attempt to write a super block to a device (device number is dnum.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.40 WARNING: sfcfs_mds:0133: read error on log partition (errno = eno errcode = ecode): mount_point

[Explanation]

An error occurred during an attempt to read the log partition of the file system (mount_point.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.41 WARNING: sfcfs_mds:0133: mount_point: metamap write error. dev = dnum block = blknum size = size

[Explanation]

An error occurred during an attempt to write the meta partition of the file system (mount_point.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.42 WARNING: sfcfs_mds:0134: read error on meta partition (errno = eno errcode = ecode): mount_point

[Explanation]

An error occurred during an attempt to read the meta partition of the file system (mount_point.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.43 WARNING: sfcfs_mds:0135: write error on log partition (errno = eno errcode = ecode): mount_point

[Explanation]

An error occurred during an attempt to write the log partition of the file system (mount_point.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.44 WARNING: sfcfs_mds:0136: write error on meta partition (errno = eno errcode = ecode): mount_point

[Explanation]

An error occurred during an attempt to write the meta partition of the file system (mount_point.)

[Action]

Take action according to the instructions in Appendix G.2.1, " Action for I/O errors."

E.3.3.1.45 WARNING: sfcfs_mds:0141: can't receive heartbeat procedure from hostname, mount_point = mount_point

[Explanation]

Communication with the AC was lost. The file system (mount_point) cannot be used from the node with the indicated host name.

[Action]

Unmount the indicated file system on the node having the host name in the message. Check the network, node, and IP address settings.

E.3.3.1.46 WARNING: sfcfs_mds:0160: mount_point: Bad file system. Remaking file system is necessary

[Explanation]

An error of the file system (mount_point) was detected. The mount operation will be failed to care the file system data.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.3.1.47 WARNING: sfcfs_mds:0160: mount_point: illegal reserve extent was found, vol = vol block = block_num size = size

[Explanation]

An error in extent-based management on the file system (mount_point) was detected.

[Action]

In all the nodes, unmount the file system in all node, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.1.48 WARNING: sfcfs_mds:0161: mount_point: illegal free extent was found, vol = vol block = block_num size = size

[Explanation]

An error in extent-based management on the file system (mount_point) was detected.

[Action]

In all the nodes, unmount the file system in all node, and execute fsck_sfcfs(1M) with -o nolog specified.

E.3.3.2 sfcfs_mount command

This section explains the sfcfs_mount command messages that is called sfcfsd daemon.

E.3.3.2.1 WARNING: sfcfs_mount: 0017: mount_point: communicate to MDS from AC failed.

[Explanation]

Access Client cannot communicate to meta-data server. So, retry again.

[Action]

No response is required.

E.3.3.2.2 WARNING: sfcfs_mount: 0018: mount_point: not enough memory

[Explanation]

Cannot get enough kernel memory. Therefore, mount the file system (mount_point) will be failed.

[Action]

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

E.3.3.2.3 WARNING: sfcfs_mount: 0037: mount_point: communicate to MDS from AC failed.

[Explanation]

Access Client cannot communicate to meta-data server. So, retry again.

[Action]

No response is required.

E.3.3.2.4 WARNING: sfcfs_mount: 0028: mount_point: quota option is not match for MDS information, so retry mount with the opposite option now.

[Explanation]

Cannot validate the quota function of the file system (mount_point), so going to invalidate the quota function.

[Action]

Validate the quota function with sfcquotaon(1M).

E.3.3.2.5 WARNING: sfcfs_mount: 0029: mount_point: retry mount failed too.

[Explanation]

Access Client cannot communicate to meta-data server. So, retry again.

[Action]

No response is required.