| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Solaris(TM) 10 Operating System) |
|
Contents
Index
|
| Appendix A List of Messages | > A.2 The GFS Shared File System Daemon messages |
This section explains the MDS (sfcfsmg daemon) warning messages of the GFS Shared File System.
Generating the daemon failed at mounting the file system (fsid) due to a failure in the lock object initialization.
Increase memory or the size of the swap area.
A daemon could not be created when mount file system.
Increase memory or the size of the swap area.
A daemon could not be created when mount file system (fsid).
Increase memory or the size of the swap area.
An error was detected in a directory entry of fsid.
Unmount the relevant file system from all of the nodes, and execute fsck_sfcfs(1M) specifying -o nolog.
An error occurred during an attempt to read the meta-data area from a device dev_num of the file system (fsid).
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred during an attempt to read the bitmap area from a device dev_num of the file system (fsid).
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred during an attempt to read the bitmap area from a device dev_num of the file system.
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred during an attempt to write to the bitmap area on a device dev_num of the file system (fsid).
Unless message sfcfs_mds:2014 or sfcfs_mds:2015 is issued, recovery by retry processing was successful, so no Response is required.
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.
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred during an attempt to write to the bitmap area on a device dev_num of the file system. Part of the file system information was lost.
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred during an attempt to write to the meta-data area on a device dev_num of the file system (fsid).
Unless message sfcfs_mds:2017 is issued, recovery by retry processing was successful, so no Response is required.
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.
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred during an attempt to write a super block to a device dev_num of the file system (fsid).
Unless message sfcfs_mds:2019 is issued, recovery was performed by retry processing, so no Response is required.
An error occurred during an attempt to write a super block to a device dev_num of the file system (fsid).
Take action according to the instructions in "C.3.1 Action for I/O errors".
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).
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".
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.
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred during an attempt to write a partition configuration data to a device dev_num of the file system (fsid).
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error in extent-based management of a file system (fsid) was detected.
Unmount the relevant file system from all of the nodes, and execute fsck_sfcfs(1M) specifying -o nolog.
An error in extent-based management of a file system (fsid) was detected.
Unmount the relevant file system, and execute fsck_sfcfs(1M) specifying -o nolog.
The super block on the device of device number (dev_num) cannot be read, when mounting the file system (fsid).
Unmount the relevant file system, and execute fsck_sfcfs(1M) specifying -o nolog.
In mounting the file system, reading from a super block on the device failed.
Unmount the relevant file system, and execute fsck_sfcfs(1M) specifying -o nolog.
Partition configuration data could not be read when mount the file system (fsid) started.
Take action according to the instructions in "C.3.1 Action for I/O errors".
Partition configuration data could not be read when mount the file system started.
Take action according to the instructions in "C.3.1 Action for I/O errors".
Information for node was not found in the file system (fsid).
Register correct node information using sfcsetup(1M).
An inconsistency was detected between the contents of the primary super block and the contents of the secondary super block on the indicated device.
Specify the partition of device number dev_num using sfcinfo(1M), 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 |
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.
Specify the partition of device number dev_num using sfcinfo(1M), 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 |
An inconsistency was found in the super block information in the indicated file system (fsid) in a multiple partition configuration.
Specify the partition of device number dev_num2 using sfcinfo(1M), 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 |
open(2) and mmap(2) that cannot be maintain the consistency of the data were issued to the same file.
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:
MDS detected a timeout at recovery mounting.
Reboot the system and perform the mounting again.
Memory could not be allocated on the file system.
Increase memory or the size of the swap area.
An error occurred, in reading from the update log area in the file system (mount_point).
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred, in reading form the meta-data area in the file system (mount_point).
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred, in writing to the update log area in the file system (mount_point).
Take action according to the instructions in "C.3.1 Action for I/O errors".
An error occurred during an attempt to write the meta partition.
Take action according to the instructions in "C.3.1 Action for I/O errors".
Communication with the AC was lost. The file system cannot be used from the node.
Unmount the indicated file system. Check the network, node, and IP address settings.
The size of the partition which constitutes the file system (fsid) might have been changed.
Please perform the procedure(from step 6 on) described on "C.3.2 Corrective action in the event of data inconsistency".
The GFS Shared File System can not be expanded by size expansion of the partition which constitutes the GFS Shared File System. Please perform the procedure above promptly.
Partition configuration information is inconsistent in the multipartition file system (fsid).
Specify the partition of device number dev_num2 using sfcinfo(1M), 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 |
|
Contents
Index
|