This section explains the sfcfs_mount command messages that is called sfcfsd daemon of the GFS Shared File System.
Explanation
The mounting failed due to a memory allocation failure.
Response
Check the system status and wait for the termination of another process or increase the swap space, and re-execute the command.
Explanation
The mounting failed due to an internal error.
Response
Collect a file output with FJQSS or fjsnap for troubleshooting information then contact field engineers.
Explanation
The file system monitoring mechanism is not operating.
Response
Check whether the file system monitoring mechanism is running.
Explanation
The specified partition (special) does not exist in the file system configuration information.
Response
Check whether the specified partition is correct.
Explanation
Reading the file system configuration information failed.
Response
Collect a file output with FJQSS or fjsnap for troubleshooting information then contact field engineers.
Explanation
The port number definition used in AC-to-MDS communication is not found.
Response
Review the port number definition in /etc/services.
Explanation
The host name information for AC-to-MDS communication cannot be obtained.
Response
Check the following points:
Setting of network is normal.
Check whether the IP addresses of the MDS nodes are correctly registered in host database (for example: /etc/inet/hosts). For details, see "11.2.2 Registering information in host database."
The file system configuration information is normal.
Execute sfcrscinfo(1M) with the -m option to check whether the host names of the MDS nodes are correct.
If the host names are not correct, change them by using sfcadm(1M) with the -u option.
If the problem cannot be solved after taking the above actions, collect a file output with FJQSS or fjsnap for troubleshooting information then contact field engineers.
For details on the commands, see sfcrscinfo(1M) and sfcadm(1M) in this manual.
Explanation
The mounting fails because it has already been mounted.
Response
Check whether the mounting has not been done with mount(1M), and take action.
If GFS is used by a Solaris Zones environment, and if a non-global zone is set to be automatically started when a global zone is started, check that the mount point mount_point is not mounted with lofs before mounting the GFS Shared File System.
# mount -p | grep mount_point |
When only the line where the forth column is lofs is output, take the following procedures to recover the failure:
Stop the non-global zone that shares the GFS Shared File System.
# zoneadm -z zonename halt |
zonename is a zone name of the non-global zone.
Mount the GFS Shared File System.
# mount mount_point |
Start the stopped non-global zone.
# zoneadm -z zonename boot |
See also "Point" in "1.8.10 GFS operational notices for Solaris Zones" to take the permanent action.
Explanation
The mounting cannot be performed because recovery processing is in progress.
Response
None.
Explanation
AC cannot connect to MDS. Therefore, mount the file system will be failed.
Response
Check MDS down. In this case, try mount again.
Explanation
An unexpected error was detected on the mounting.
Possible causes:
The special or mountpoint specified is invalid.
The network setting of a shared node is invalid.
The host name of a shared node specified is invalid.
The shared node fails during command execution.
Response
Execute mount_sfcfs(1M) again after correcting the cause of the failure according to the following procedures:
Check whether a file and a directory specified with special and mountpoint exist. If the specification is not correct, specify the correct special and mountpoint. Create the directory specified with mountpoint, if it has not been created.
Check whether the IP address of the node that shares the file system is correctly registered in host database (for example: /etc/inet/hosts). For details, see "11.2.2 Registering information in host database."
Execute sfcinfo(1M) with the -n and -a options to check whether the host name of a shared node is correct. If the host name is not correct, change it by using sfcadm(1M) with -u option.
If any warning message was output immediately before this message, take an action to deal with the warning message.
If the problem cannot be solved by the response above, collect the diagnostic data with FJQSS or fjsnap and contact field engineers.
For details on the commands, see sfcinfo(1M) and sfcadm(1M) in this manual.
Explanation
An unknown error was detected.
Response
Collect a file output with FJQSS or fjsnap for troubleshooting information then contact field engineers.
Explanation
Opening of the partition (special) failed.
Response
Take corrective action according the detailed information errmsg.
Explanation
Reading of the super block information or partition configuration information on the partition (special) failed.
Response
Collect a file output with FJQSS or fjsnap for troubleshooting information then contact field engineers.
Explanation
The specified partition (special) is not of the GFS Shared File System.
Response
Specify a special file that is being used for the GFS Shared File System.
Explanation
An invalid value was detected in the tuning parameter param for the file system.
Response
Collect a file output with FJQSS or fjsnap for troubleshooting information then contact field engineers.
