| 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) information messages of the GFS Shared File System.
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.)
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 (fsid).
Delete unnecessary files or move files to a file system that has enough space.
There is no more space in V-data area of the file system (fsid).
Delete unnecessary files or move files to a file system that has enough space.
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.
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.
An illegal path name request was made in a directory operation of the file system (fsid).
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 ino and the operation making the illegal request, and take appropriate action.
The system could not write an update log on device dev_num of the file system (fsid).
Unless message sfcfs_mds:2020 is issued, recovery by retry processing was successful, so no Response is required.
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.
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".
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.
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".
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.
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".
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.
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".
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.
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".
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.
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".
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.
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".
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.
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".
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.
Unmount the file system, and make the super blocks consistent using sfcadm(1M).
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.
Unmount the file system, and make the super blocks consistent using sfcadm(1M).
A node with an existing hostid and nonexistent node name was registered in the file system.
Unless sfcfs_mds:2030 is issued, no Response is required.
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.
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.
Releasing i-node's cache memory (vnode) is stopped because i-node's cache memory reached the low_num.
None.
|
Contents
Index
|