| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment) |
|
Contents
Index
|
| Appendix E List of Messages | > E.3 GFS Shared File System Daemon messages |
This section explains the information messages of each GFS Shared File System daemon.
sfcfrmd daemon was started as a master.
None.
sfcfrmd daemon was started as a slave.
None.
Service of sfcfrmd daemon was started.
None.
Service of sfcfrmd daemon was completed.
None.
The system recognized the configuration node with CIP host name CIPname and host ID hostid.
None.
The node with CIP host name CIPname and host ID hostid was added to the node configuration information.
None.
There is no more space in file data area of the file system (mount_point.)
(For an ordinary user, this message is also output when space drops below the minfree limit.)
Expand the file system, delete unnecessary files, or move files to a file system that has enough space. To expand the file system, use sfcadd(1M).
There is no more space in I-node area of the file system (mount_point.)
Expand the file system, delete unnecessary files or move files to a file system that has enough space. To expand the file system, use sfcadd(1M).
There is no more space in V-data area of the file system (mount_point.)
Expand the file system, delete unnecessary files or directories, or move files to a file system that has enough space. To expand the file system, use sfcadd(1M).
There is no more area for managing unused space in the file system (mount_point) because of area fragmentation. An area released by subsequent area release processing may become an invalid area.
Back up the file system, and then re-create and restore it to unfragment the fragmented areas in the file system.
An error was detected in the i-node in a file system (mount_point), but the i-node recovered automatically from the error.
No response is required because the system makes the correction and continues processing.
An illegal path name request was made in a directory operation for the file system (mount_point.)
No response is required because the system rejected the illegal request and continues processing. If this error occurs frequently, identify the target directory using parent inode number (inum) and the operation making the illegal request, and take appropriate action.
The system could not write an update log of the file system (mount_point) on the device (device number is dnum.)
Unless message sfcfs_mds:0042 is issued, recovery by retry processing was successful, so no response is required.
A value that exceeded the specified range was originally specified in sfcfs_ninode, but this value was changed appropriately.
No response is required because the system corrects the value and continues processing. If the value of sfcfs_ninode was specified in /etc/system, review the value.
The file system management detected an attempt to release the wrong file system.
No response is required because the system corrects the error and continues processing.
An error was detected in the file system (mount_point) but was resolved automatically.
No response is required because the system continues processing after correcting the error automatically.
The primary super block of the file system (mount_point) on the device (device number is dnum) could not be read. Processing was continued because the secondary super block was read correctly.
File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in Appendix G.2.1, " Action for I/O errors."
The secondary super block of the file system (mount_point) on the device (device number is dnum) could not be read. Processing was continued because the primary super block was read correctly.
File system manipulation can be continued. However, because a block error occurred, promptly take action according to the instructions in Appendix G.2.1, " Action for I/O errors."
The size of the specified partition on the device (device number is dnum) could not be obtained. Processing was continued because the primary super block was read correctly.
Unmount the file system in all nodes, and make the super blocks consistent using sfcadm(1M).
Primary partition configuration data of the file system (mount_point) on the device (device number is dnum) could not be read. Processing was continued because the secondary partition configuration data was read correctly.
File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in Appendix G.2.1, " Action for I/O errors."
Secondary partition configuration data of the file system (mount_point) on the device (device number is dnum) could not be read. Processing was continued because the primary partition configuration data was read correctly.
File system operation can be continued. However, because a block error occurred, promptly take action according to the instructions in Appendix G.2.1, " Action for I/O errors."
A node with an existing hostid and nonexistent node name was registered in the file system (mount_point.)
Unless sfcfs_mds:0080 is issued, no response is required.
The file system (mount_point) is recovered using update log.
No response is required.
An error was detected i-node managements of the file system (mount_point) but was resolved automatically.
No response is required because the system makes the correction and continues processing.
daemon of GFS Shared File System finished abnormally.
Collect the diagnostic data with fjsnap and contact local Customer Support.
|
Contents
Index
|