| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment) |
|
Contents
Index
|
| Appendix E List of Messages | > E.1 AC Messages of GFS Shared File System |
This section explains AC (kernel) information messages of the GFS Shared File System.
There is no more file system (mount_point) data area.
(For a non-privileged 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).
The value set for sfcfs_ninode was changed to max_value because it exceeded the specified value.
No response is required because the system makes the correction and continues processing. After specifying the sfcfs_ninode value in /etc/system, be sure to check it.
File system management detected release of the wrong file system (fsid.)
No response is required because the system makes the correction and continues processing.
The primary super block 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 on the device (device number is dnum) could not be read. Processing was continued because the primary 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."
Primary partition configuration data 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 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 host id and nonexistent node name was registered in the file system (mount_point.)
Unless message sfcfs:0080 is issued, no response is required.
The specified file (inum) on the file system (mount_point) to mmap(2) is currently being open(2) on an other node.
The file cannot be mapped to maintain the consistency of the data.
Please wait for the termination of the process running on the node1 indicated in the message "sfcfs_mds:0112", and execute again.
Some processes work correctly even if this message and the message "sfcfs_mds:0112" were issued. In this case, these messages can be ignored.
An error is detected during recovery for the file system (mount_point.)
No response is required.
An error is detected during online addition of partition(s) on mount_point.
Respond according to a message displayed by sfcadd(1M). When sfcadd(1M) terminates abnormally, check the environment and re-execute the sfcadd(1M).
The file to be opened is under mmap(2) on another node. To ensure data consistency, the file cannot be opened.
Wait until the application on the node appearing on node1 of message sfcfs_mds:0112 has terminated, then re-execute.
The number of the files which user unum owns on mount_point was reached to the hard limit value of the number of files set up by the quota function. User unum cannot own a file any more.
In order for user unum to enable create a new file, please delete unnecessary files which user unum owns on mount_point until the number of files is less than the soft limit value and hard limits value set by quota function.
The number of files whitch user unum owns on mount_point exceeds the soft limit value set by quota function.
In order for user unum to enable create a new file, please delete unnecessary files which user unum owns on mount_point until the number of files is less than the soft limit value and hard limits value set by quota function.
The number of the files which user unum owns on mount_point was not less than the soft limit value in the time limit set up by the quota function, after it exceeding the soft limit value. User unum cannot create a new file until it is less than a soft limit value.
In order for user unum to enable create a new file, please delete unnecessary files which user unum owns on mount_point until the number of files is less than the soft limit value and hard limits value set by quota function.
The total of the number of use blocks of a file which user unum owns on mount_point reached to the hard limit value of the number of blocks set up by the quota function. User unum cannot use a block any more.
In order for user unum to enable allocate a new block, please delete unnecessary files which user unum owns on mount_point until the number of use blocks is less than the soft limit value and hard limits value set by quota function.
The total of the number of use blocks of a file which user unum owns on mount_point reached to the soft limit value of the number of blocks set up by the quota function.
In order for user unum to enable allocate a new block, please delete unnecessary files which user unum owns on mount_point until the number of use blocks is less than the soft limit value and hard limits value set by quota function.
The total of the number of use blocks of a file which user unum owns on mount_point was not less than the soft limit value in the time limit set up by the quota function, after it exceeding the soft limit value. User unum cannot get a new block until it is less than a soft limit value.
In order for user unum to enable allocate a new block, please delete unnecessary files which user unum owns on mount_point until the number of use blocks is less than the soft limit value and hard limits value set by quota function.
The same data (hostname) is repeatedly specified in the host specification for the file system (mount_point.) Operation continues by excluding invalid entries.
Check that the multiple LAN specification is done properly.
Communication path to MDS is closed temporarily by a change command for the file system (mount_point.)
No countermeasures need to be applied.
Re-connection to MDS for the file system (mount_point) is completed.
No countermeasures need to be applied.
|
Contents
Index
|