| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Linux) |
|
Contents
Index
|
| Appendix A List of Messages | > A.2 GFS Shared File System Daemon messages | > A.2.3 Warning messages |
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 sfcfsck(8) specifying -o nolog.
An error occurred during an attempt to read the meta-data area from a device dev_num.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to read the bitmap area from a device dev_num.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to read the bitmap area from a device dev_num.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to write to the bitmap area on a device dev_num.
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. Part of the file system (fsid) information was lost.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to write to the bitmap area on a device dev_num. Part of the file system (fsid) information was lost.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to write to the meta-data area on a disk.
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 disk. Part of the file system (fsid) information was lost.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to write a super block to a disk.
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 disk.
Take action according to the instructions in "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.
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 "Action for I/O errors."
The file system was blockaded due to a writing error to the super block on the device number dev_num in the file system (fsid). In the future, access to this file system will be an error return.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to write a partition configuration data to a disk.
Take action according to the instructions in "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 sfcfsck(8) specifying -o nolog.
An error in extent-based management of a file system (fsid) was detected.
Unmount the relevant file system, and execute sfcfsck(8) specifying -o nolog.
An error in extent-based management of a file system (fsid) was detected.
Unmount the relevant file system, and execute sfcfsck(8) specifying -o nolog.
A super block could not be read when the mount the file system (fsid) started
Unmount the relevant file system, and execute sfcfsck(8) specifying -o nolog.
Partition configuration data could not be read when mount the file system (fsid) started.
Take action according to the instructions in "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 "Action for I/O errors."
Information for node was not found in the file system (fsid).
Register correct node information using sfcsetup(8).
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(8), and perform the procedure of "Action to be taken when the file system configuration information is inconsistent"
# sfcinfo -d dev_num
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(8), and perform the procedure of "Action to be taken when the file system configuration information is inconsistent"
# sfcinfo -d dev_num
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_num using sfcinfo(8), and perform the procedure of "Action to be taken when the file system configuration information is inconsistent"
# sfcinfo -d dev_num
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:
i) determine the filename of the i-number, using find(1) with -inum option.
ii) determine the process ID that uses the filename, using fuser(1).
iii) determine the command name of the process ID, using ps(1).
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 during an attempt to read the log partition.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to read the meta partition.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to write the log partition.
Take action according to the instructions in "Action for I/O errors."
An error occurred during an attempt to write the meta partition.
Take action according to the instructions in "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 "Action to be taken when the file system configuration information is inconsistent".
The file system can keep on using. But 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.
|
Contents
Index
|