Top
PRIMECLUSTER Global File Services Configuration and Administration Guide 4.6
FUJITSU Software
Appendix A List of Messages > A.2 GFS Shared File System Daemon messages > A.2.9 Warning messages (MDS (sfcfsmg daemon))
PreviousNext

A.2.9 Warning messages (MDS (sfcfsmg daemon))

This section explains the MDS (sfcfsmg daemon) warning messages of the GFS Shared File System.

WARNING: sfcfs_mds:2001: fsid: daemon create failed(lock_init failed). errcode=errcode

Explanation

Generating the daemon failed at mounting the file system (fsid) due to a failure in the lock object initialization.

Response

Increase memory or the size of the swap area.

WARNING: sfcfs_mds:2002: daemon create failed(can't create thread).

Explanation

A daemon could not be created when mount file system.

Response

Increase memory or the size of the swap area.

WARNING: sfcfs_mds:2003: fsid:daemon create failed(can't creat thread).

Explanation

A daemon could not be created when mount file system (fsid).

Response

Increase memory or the size of the swap area.

WARNING: sfcfs_mds:2004: fsid: bad dir: invalid offset. ino=ino-num offset=offset
WARNING: sfcfs_mds:2007: fsid: bad dir: size error. ino=ino-num size=size

Explanation

An error was detected in a directory entry of fsid.

Response

Unmount the relevant file system from all of the nodes, and execute sfcfsck(8) specifying -o nolog.

WARNING: sfcfs_mds:2008: fsid: meta data read error. type=number dev=dev_num block=block_num size=size errcode=errcode
WARNING: sfcfs_mds:2009: fsid: meta data read error. type=number dev=dev_num block=block_num size=size errcode=errcode

Explanation

An error occurred during an attempt to read the meta-data area from a device dev_num of the file system (fsid).

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2010: fsid: bitmap read error. type=number dev=dev_num block=block_num size=size errcode=errcode
WARNING: sfcfs_mds:2011: fsid: bitmap read error. type=number dev=dev_num block=block_num size=size errcode=errcode

Explanation

An error occurred during an attempt to read the bitmap area from a device dev_num of the file system (fsid).

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2012: bitmap read error. type=number dev=dev_num block=block_num size=size errcode=errcode

Explanation

An error occurred during an attempt to read the bitmap area from a device dev_num of the file system.

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2013: fsid: bitmap write error.type=number dev=dev_num block=block_num size=size errcode=errcode

Explanation

An error occurred during an attempt to write to the bitmap area on a device dev_num of the file system (fsid).

Response

Unless message sfcfs_mds:2014 is issued, recovery by retry processing is successful. Therefore, no response is required.

WARNING: sfcfs_mds:2014: fsid: bitmap write error information was lost. type=number dev=dev_num block=block_num size=size errcode=errcode

Explanation

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

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2016: fsid: meta data write error. type=number dev=dev_num block=block_num size=size errcode=errcode

Explanation

An error occurred during an attempt to write to the meta-data area on a device dev_num of the file system (fsid).

Response

Unless message sfcfs_mds:2017 is issued, recovery by retry processing is successful. Therefore, no response is required.

WARNING: sfcfs_mds:2017: fsid: meta data write error information was lost. type=number dev=dev_num block=block_num size=size errcode=errcode

Explanation

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

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2018: fsid: super block write error. dev=dev_num block=block_num size=size errcode=errcode

Explanation

An error occurred during an attempt to write a super block to a device dev_num of the file system (fsid).

Response

Unless message sfcfs_mds:2019 is issued, recovery by retry processing is successful. Therefore, no response is required.

WARNING: sfcfs_mds:2019: fsid: super block write error information was lost. dev=dev_num block=block_num size=size errcode=errcode

Explanation

An error occurred during an attempt to write a super block to a device dev_num of the file system (fsid). Part of the file system information was lost.

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2020: fsid: LOG daemon is dead

Explanation

The log daemon stopped processing because it could not recover from a failure to write to the update log area on the file system (fsid).

Response

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. Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2021: fsid: cannot access, too many I/O errors. dev=dev_num

Explanation

The file system (fsid) was blockaded due to a writing error to the super block on the device number dev_num in the file system. In the future, access to this file system will be an error return.

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2022: fsid: volume information write error. dev=dev_num block=block_num size=size errcode=errcode
WARNING: sfcfs_mds:2023: fsid: volume information write error. dev=dev_num block=block_num size=size errcode=errcode

Explanation

An error occurred during an attempt to write a partition configuration data to a device dev_num in the file system (fsid).

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2024: fsid: cannot delete extents. ino=number offset=offset block=block errcode=errcode

Explanation

An error in extent-based management of a file system (fsid) was detected.

Response

Unmount the relevant file system from all of the nodes, and execute sfcfsck(8) specifying -o nolog.

WARNING: sfcfs_mds:2026: fsid: super block read error. dev=dev_num errcode=errcode

Explanation

The super block on the device of device number (dev_num) cannot be read, when mounting the file system (fsid).

Response

Unmount the relevant file system, and execute sfcfsck(8) specifying -o nolog.

WARNING: sfcfs_mds:2027: super block read error. errcode=errcode

Explanation

In mounting the file system, reading from a super block on the device failed.

Response

Unmount the relevant file system, and execute sfcfsck(8) specifying -o nolog.

WARNING: sfcfs_mds:2028: fsid: partition configuration read error. dev=dev_num errcode=errcode

Explanation

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

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2029: partition configuration read error. errcode=errcode

Explanation

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

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2030: fsid: node information not found for node

Explanation

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

Response

Register correct node information using sfcsetup(8).

WARNING: sfcfs_mds:2031: fsid: primary and secondary super blocks are different. dev=dev_num

Explanation

An inconsistency was detected between the contents of the primary super block and the contents of the secondary super block on the indicated device.

Response

Specify the partition of device number dev_num using sfcinfo(8), and perform the procedure of "C.3.2 Corrective action in the event of data inconsistency."

# sfcinfo -d dev_num <Enter>
/dev/sfdsk/gfs01/dsk/volume01:
FSID special                                      size  Type  mount
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num)      14422  META  /mnt
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num)       5116  LOG   /mnt
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num)      95112  DATA  /mnt

WARNING: sfcfs_mds:2032: fsid: primary and secondary volume informations are different. dev=dev_num

Explanation

An inconsistency was detected between the contents of the primary partition configuration data and the contents of the secondary partition configuration data on the device.

Response

Specify the partition of device number dev_num using sfcinfo(8), and perform the procedure of "C.3.2 Corrective action in the event of data inconsistency."

# sfcinfo -d dev_num <Enter>
/dev/sfdsk/gfs01/dsk/volume01:
FSID special                                      size  Type  mount
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num)      14422  META  /mnt
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num)       5116  LOG   /mnt
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num)      95112  DATA  /mnt

WARNING: sfcfs_mds:2033: fsid: super blocks differ. dev dev_num1 to dev_num2

Explanation

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

Response

Specify the partition of device number dev_num2 using sfcinfo(8), and perform the procedure of "C.3.2 Corrective action in the event of data inconsistency."

# sfcinfo -d dev_num2 <Enter>
/dev/sfdsk/gfs01/dsk/volume01:
FSID special                                       size  Type  mount
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num2)      14422  META  /mnt
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num2)       5116  LOG   /mnt
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num2)      95112  DATA  /mnt

WARNING: sfcfs_mds:2034: mmap can't access between other nodes fsid=fsid ino=i-number nodename(node1,node2) mode(mode1,mode2)

Explanation

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

Response

Please wait for the termination of the process running on the "node1" indicated this message, and execute again.
To determine the process using the i-number, 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 that uses the filename, using fuser(1).

  3. determine the command name of the process ID, using ps(1).

WARNING: sfcfs_mds:2035: MDS(recover) is timed out

Explanation

MDS detected a timeout at recovery mounting.

Response

Reboot the system and perform the mounting again.

WARNING: sfcfs_mds:2036: can't allocate memory in primary

Explanation

Memory could not be allocated on the file system.

Response

Increase memory or the size of the swap area.

WARNING: sfcfs_mds:2037: read error on log partition(errno=errno errcode=errcode): mount_point

Explanation

An error occurred, in reading from the update log area in the file system (mount_point).

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2038: read error on meta partition(errno=errno errcode=error_code): mount_point

Explanation

An error occurred, in reading from the meta-data area in the file system (mount_point).

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2039: write error on log partition(errno=errno errcode=error_code): mount_point

Explanation

An error occurred, in writing to the update log area in the file system (mount_point).

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2040: write error on meta partition(errno=errno errcode=error_code): mount_point

Explanation

An error occurred during an attempt to write the meta partition.

Response

Take action according to the instructions in "C.3.1 Action for I/O errors."

WARNING: sfcfs_mds:2042: fsid: The size of the partition might have been changed after the file system was made.

Explanation

The size of the partition which constitutes the file system (fsid) might have been changed.

Response

Perform the procedure (from step 6 on) described on "C.3.2 Corrective action in the event of data inconsistency."

GFS Shared File System can not be expanded by size expansion of the partition which shares the GFS Shared File System. Perform the procedure above promptly.

WARNING: sfcfs_mds:2043: fsid: volume informations differ. dev dev_num1 to dev_num2

Explanation

Partition configuration information is inconsistent in the multipartition file system (fsid).

Response

Specify the partition of device number dev_num2 using sfcinfo(8), and perform the procedure of "C.3.2 Corrective action in the event of data inconsistency."

# sfcinfo -d dev_num2 <Enter>
/dev/sfdsk/gfs01/dsk/volume01:
FSID special                                       size  Type  mount
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num2)      14422  META  /mnt
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num2)       5116  LOG   /mnt
   1 /dev/sfdsk/gfs01/dsk/volume01(dev_num2)      95112  DATA  /mnt

WARNING: sfcfs_mds:2046: fsid: invalid parameter(param)

Explanation

An invalid value was detected in the tuning parameter param for the file system.

Response

Check whether the tuning parameter is correctly set. For details, see "14.1 Tuning Parameters" in this manual.

PreviousNext
Copyright FUJITSU LIMITED 2019-2021