PRIMECLUSTER Global File Services Configuration and Administration Guide 4.6

A.2.13 Information messages (MDS (sfcfsmg daemon))

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

NOTICE: sfcfs_mds:3001: fsid: file system full

Explanation

There is no more space in file data area of the file system (fsid).
(For an ordinary user, this message is also output when space drops below the minfree limit.)

Response

Perform any of the following procedures to expand the space of the file system:

• 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.

NOTICE: sfcfs_mds:3002: fsid: out of inodes

Explanation

There is no more space in i-node area of the file system (fsid).

Response

Delete unnecessary files or move files to a file system that has enough area.

NOTICE: sfcfs_mds:3003: fsid: file system meta data full(Vdata) type=number

Explanation

There is no more space in V-data area of the file system (fsid).

Response

Delete unnecessary files or move files to a file system that has enough area.

NOTICE: sfcfs_mds:3004: fsid: too much fragment(extent)

Explanation

There is no more area for managing unused space in the file system (fsid) because of area fragmentation. An area released by subsequent area release processing may become an invalid area.

Response

To sort out fragmented area in the file system, back up each file in the file system, and recreate the file system then restore the backed up data.

NOTICE: sfcfs_mds:3006: fsid: I/O error on log. dev=dev_num block=block_num, size=size errcode=errcode

Explanation

The system could not write an update log on device dev_num of the file system (fsid).

Response

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

NOTICE: sfcfs_mds:3007: fsid: primary super block read failed, but secondary read. dev=dev_num block=block_num size=size errcode=errcode

Explanation

The primary super block on the device dev_num of the file system (fsid) could not be read. Processing was continued because the secondary super block was read correctly.

Response

File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in "C.3.1 Action for I/O errors."

NOTICE: sfcfs_mds:3008: primary super block read failed, but secondary read. errcode=errcode

Explanation

The primary super block on the device of the file system could not be read. Processing was continued because the secondary super block was read correctly.

Response

File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in "C.3.1 Action for I/O errors."

NOTICE: sfcfs_mds:3009: fsid: secondary super block read failed, but primary read. dev=dev_num block=block_num size=size errcode=errcode

Explanation

The secondary super block on the device dev_num of the file system (fsid) could not be read. Processing was continued because the primary super block was read correctly.

Response

File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in "C.3.1 Action for I/O errors."

NOTICE: sfcfs_mds:3010: secondary super block read failed, but primary read. errcode=errcode

Explanation

The secondary super block on the device of the file system could not be read. Processing was continued because the primary super block was read correctly.

Response

File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in "C.3.1 Action for I/O errors."

NOTICE: sfcfs_mds:3011: fsid: primary partition configuration read failed, but secondary read. dev=dev_num block=block_num size=size errcode=errcode

Explanation

Primary partition configuration data on the device dev_num of the file system (fsid) could not be read. Processing was continued because the secondary partition configuration data was read correctly.

Response

File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in "C.3.1 Action for I/O errors."

NOTICE: sfcfs_mds:3012: primary partition configuration read failed, but secondary read. errcode=errcode

Explanation

Primary partition configuration data on the device of the file system could not be read. Processing was continued because the secondary partition configuration data was read correctly.

Response

File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in "C.3.1 Action for I/O errors."

NOTICE: sfcfs_mds:3013: fsid: secondary partition configuration read failed, but primary read. dev=dev_num block=block_num size=size errcode=errcode

Explanation

Secondary partition configuration data on the device dev_num of the file system (fsid) could not be read. Processing was continued because the primary partition configuration data was read correctly.

Response

File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in "C.3.1 Action for I/O errors."

NOTICE: sfcfs_mds:3014: secondary partition configuration read failed, but primary read. errcode=errcode

Explanation

Secondary partition configuration data on the device of the file system could not be read. Processing was continued because the primary partition configuration data was read correctly.

Response

File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in "C.3.1 Action for I/O errors."

NOTICE: sfcfs_mds:3015: fsid: can't get partition size. dev=dev_num: error=errcode

Explanation

The size of the specified partition on the device dev_num of the file system (fsid) could not be obtained. Processing was continued because the primary super block was read correctly.

Response

Unmount the file system, and make the super blocks consistent using sfcadm(8).

NOTICE: sfcfs_mds:3016: can't get partition size

Explanation

The size of the specified partition on the device of the file system could not be obtained. Processing was continued because the primary super block was read correctly.

Response

Unmount the file system, and make the super blocks consistent using sfcadm(8).

NOTICE: sfcfs_mds:3017: nodename mismatch. node<->node

Explanation

A node with an existing hostid and nonexistent node name was registered in the file system.

Response

Unless sfcfs_mds:2030 is issued, no response is required.

NOTICE: sfcfs_mds:3020: mountpoint: The total number of vnodes used reached the upper bound. vnodes used=total_num: upper bound=high_num: lower bound=low_num

Explanation

i-node's cache memory (vnode) is released until total_num falls below the low_num because total_num of i-node's cache memory amounted to high_num.

Response

The file system operation can be continued. But limit operations to the bare minimum until message (sfcfs_mds:3021) is output, because i-node's cache memory is being released.

NOTICE: sfcfs_mds:3021: mountpoint: The total number of vnodes used(=total_num) is the lower bound(=low_num).

Explanation

Releasing i-node's cache memory (vnode) is stopped because i-node's cache memory reached the low_num.

Response

None.