PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)
Contents Index PreviousNext
Appendix E List of Messages> E.3 GFS Shared File System Daemon messages

E.3.2 Error messages

This section explains the error messages of each GFS Shared File System daemon.

E.3.2.1 sfcfrmd daemon

E.3.2.1.1 ERROR:sfcfrmd:0001: not superuser

[Explanation]

sfcfrmd daemon is not performed by super user

[Action]

Please start sfcfrmd daemon by sfcfrmstart(1M) command as a super user.

E.3.2.1.2 ERROR:sfcfrmd:0002: associated with a terminal device

[Explanation]

The sfcfrmd daemon is direct performed.

[Action]

Please start sfcfrmd daemon by sfcfrmstart(1M) command as a super user.

E.3.2.1.3 ERROR:sfcfrmd:0003: cannot read pathname, or something wrong

[Explanation]

Since there was injustice or file reading of pathname went wrong, sfcfrmd daemon starting went wrong.

[Action]

Please check whether the file of pathname is set up correctly.

E.3.2.1.4 ERROR:sfcfrmd:0004: cannot get node version string

[Explanation]

The sfcfrmd daemon failed to start, because a working file string in /var/opt/FJSVsfcfs was broken.

[Action]

Make sure that /var/opt directory has a space by df(1M) command and re-start the node.

E.3.2.1.5 ERROR:sfcfrmd:0005: something wrong in pathname

[Explanation]

The sfcfrmd daemon failed to start, because /etc/services has no entry of sfcfsrm or pathname is broken.

[Action]

Make sure that each /etc/services file has the entry "sfcfsrm 9200/tcp in all the nodes in the cluster. If not, add it. For details of this file, see the services(4) of the "Solaris X Reference Manual Collection."

If the setting above is right, pathname seems broken. Collect the diagnostic data with fjsnap and contact local Customer Support.

E.3.2.1.6 ERROR:sfcfrmd:0006: cannot allocate memory space

[Explanation]

Since acquisition of a memory went wrong, sfcfrmd daemon starting went wrong.

[Action]

Please check the state of a system, and wait for the end of other processes, or increase swap space and reboot the node.

E.3.2.1.7 ERROR:sfcfrmd:0007: cannot start service

[Explanation]

Failed to start the sfcfrmd daemon.

[Action]

Obtain a core dumping of sfcfrmd daemon by gcore(1) in all the nodes (for example, "/usr/bin/ps -e | grep sfcfrmd" to get the process id and "/usr/bin/gcore process_id".) In addition to this, collect the diagnostic data with fjsnap and contact local Customer Support.

E.3.2.1.8 ERROR:sfcfrmd:0008: I/O error or data corruption of management partition: pathname

[Explanation]

sfcfrmd daemon failed in reading and writing for the management partition (pathname.)

[Action]

Please check whether a setup as a management partition domain of the GFS Shared File System is right, or a disk operates normally.

E.3.2.1.9 ERROR:sfcfrmd:0009: something wrong in cluster settings

[Explanation]

Since a cluster was not started, sfcfrmd daemon starting went wrong.

[Action]

Please start a cluster.

E.3.2.1.10 ERROR:sfcfrmd:0010: cannot get host name

[Explanation]

The CIP address registered in the management partition changed.

[Action]

By remaking and restoring the management partition, back the configuration of the partition to a previous one before a value of the CIP address changed. For details to remake and restore, see Section 20.5, " Backup of the management partition information." and Section 20.6, "Restoration of the management partition information."

E.3.2.1.11 ERROR:sfcfrmd:0011: cannot connect to sfcprmd

[Explanation]

The sfcfrmd daemon failed to connect the sfcprmd daemon.

[Action]

Make sure that the sfcprmd daemon is running by ps(1) command (for example, "/usr/bin/ps -e | grep sfcprmd".) If the sfcprmd daemon was stopped by the unload dependency script, restart sfcprmd by the load script ("/opt/SMAW/SMAWcf/dep/start.d/S81sfcfs load".) Otherwise, re-start the node.

If this message appeared when sfcprmd daemon is running, collect the investigation material using the fjsnap command and contact local Customer Support.

E.3.2.1.12 ERROR:sfcfrmd:0012: cannot connect to sfchnsd

[Explanation]

The sfcfrmd daemon failed to connect the sfchnsd daemon.

[Action]

Make sure that the sfchnsd daemon is running by ps(1) command (for example, "/usr/bin/ps -e | grep sfchnsd".) If the sfchnsd daemon was stopped by the unload dependency script, restart sfchnsd by the load script ("/opt/SMAW/SMAWcf/dep/start.d/S81sfcfs load".) Otherwise, re-start the node.

If this message appeared when sfchnsd daemon is running, collect the investigation material using the fjsnap command and contact local Customer Support.

E.3.2.1.13 ERROR:sfcfrmd:0013: cannot activate sfchnsd

[Explanation]

sfchnsd daemon is not activated.

[Action]

Obtain a core dumping of sfchnsd daemon by gcore(1) (for example, "/usr/bin/ps -e | grep sfchnsd" to get the process id and "/usr/bin/gcore process_id".) In addition to this, collect the diagnostic data with fjsnap and contact local Customer Support.

E.3.2.1.14 ERROR:sfcfrmd:0014: cannot get service port

[Explanation]

A service port is not able to be acquired.

[Action]

Make sure that each /etc/services file has the entry "sfcfsrm 9200/tcp in all the nodes in the cluster. If not, add it. For details of this file, see the services(4) of the "Solaris X Reference Manual Collection."

E.3.2.1.15 ERROR: sfcfrmd:0024: cannot start service while adding a node

[Explanation]

The sfcfrmd daemon failed to start, because node configuration information was being added to the management partition.

[Action]

After addition of the node configuration information is completed, start sfcfrmd daemon by sfcfrmstart(1M) command. To check whether addition of the node configuration information was completed, execute sfcsetup(1M) without any arguments, and check that information on the added node is displayed in the displayed contents.

E.3.2.2 MDS(sfcfsmg) daemon

E.3.2.2.1 ERROR: sfcfs_mds:0001: can't execute MDS for mount_point, errcode=ecode

E.3.2.2.2 ERROR: sfcfs_mds:0002: can't execute MDS for special

E.3.2.2.3 ERROR: sfcfs_mds:0003: can't execute MDS

[Explanation]

The meta-data server could not be started.

[Action]

Contact local Customer Support.

E.3.2.2.4 ERROR: sfcfs_mds:0004: can't execute primary MDS for mount_point, errcode=ecode

[Explanation]

The primary meta-data server for the file system (mount_point) could not be started.

[Action]

Contact local Customer Support.

E.3.2.2.5 ERROR: sfcfs_mds:0005: can't execute secondary MDS for mount_point, errcode=ecode

[Explanation]

The secondary meta-data server for the file system (mount_point) could not be started.

[Action]

Contact local Customer Support.

E.3.2.2.6 ERROR: sfcfs_mds:0006: can't take over MDS for mount_point, errcode=ecode

[Explanation]

The meta-data server for the file system (mount_point) switch processing failed.

[Action]

Contact local Customer Support.

E.3.2.2.7 ERROR: sfcfs_mds:0007: primary MDS for mount_point terminated, errcode=ecode

[Explanation]

The primary meta-data server for the file system (mount_point) terminated abnormally.

[Action]

Contact local Customer Support.

E.3.2.2.8 ERROR: sfcfs_mds:0008: secondary MDS for mount_point terminated, errcode=ecode

[Explanation]

The secondary meta-data server for the file system (mount_point) terminated abnormally.

[Action]

Contact local Customer Support.

E.3.2.2.9 ERROR: sfcfs_mds:0021: mount_point: illegal operation: op= code

[Explanation]

An illegal operation was detected during processing in a file system (mount_point.)

[Action]

Obtain a core dumping, and contact local Customer Support.

E.3.2.2.10 ERROR: sfcfs_mds:0021: can't allocate memory in primary MDS for mount_point, errcode=ecode

[Explanation]

Cannot allocate memory in primary MDS for the file system (mount_point.) Memory of system is insufficient.

[Action]

Increase the swap space or real memory.

E.3.2.2.11 ERROR: sfcfs_mds:0022: can't allocate memory in secondary MDS for mount_point, errcode=ecode

[Explanation]

Cannot allocate memory in secondary MDS for the file system (mount_point.) Memory of system is insufficient.

[Action]

Increase the swap space or real memory.

E.3.2.2.12 ERROR: sfcfs_mds:0023: can't allocate memory in taking over MDS for mount_point, errcode=ecode

[Explanation]

Cannot allocate memory in taking over of MDS for the file system (mount_point.) Memory of system is insufficient.

[Action]

Increase the swap space or real memory.

E.3.2.2.13 ERROR: sfcfs_mds:0025: mount_point: invalid slot status code

[Explanation]

An inconsistency occurred during processing in the file system (mount_point.)

[Action]

Obtain a core dumping, and contact local Customer Support.

E.3.2.2.14 ERROR: sfcfs_mds:0031: MDS for mount_point terminated because logreplay failed

[Explanation]

The meta-data server for the file system (mount_point) log replay failed.

[Action]

Contact local Customer Support.

E.3.2.2.15 ERROR: sfcfs_mds:0052: v_count != 0 ino_pointer inum

[Explanation]

An error was detected in a released i-node (inum) in a file system.

[Action]

Obtain a core dump and contact local Customer Support.

E.3.2.2.16 ERROR: sfcfs_mds:0053: mount_point: illegal transaction buffer. bufno = number

E.3.2.2.17 ERROR: sfcfs_mds:0054: mount_point: illegal transaction buffer. bufno = number

E.3.2.2.18 ERROR: sfcfs_mds:0055: mount_point: buffer overflow. size = size

[Explanation]

An error detected in update log management of file system (mount_point.)

[Action]

Obtain a core dump and contact local Customer Support.

E.3.2.2.19 ERROR: sfcfs_mds:0056: mount_point: hold count is invalid. type = tnum number = num

[Explanation]

An error was detected in the file system data reference count.

[Action]

Obtain a core dump and contact local Customer Support.

E.3.2.3 sfcfsd daemon

E.3.2.3.1 ERROR: sfcfsd: 0001: gfs monitor daemon for mountpoint (mount_point) abort: detail

E.3.2.3.2 ERROR: sfcfsd: 0002: gfs monitor daemon for fsid(fsid) abort: detail

E.3.2.3.3 ERROR: sfcfsd: 0003: gfs monitor daemon abort: detail

[Explanation]

The GFS Shared File System monitoring daemon ended abnormally. The error explained in detail occurred.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.3.4 ERROR: sfcfsd: 0004: can't execute primary MDS: mountpoint(mount_point)

[Explanation]

Starting up the primary MDS for the file system (mount_point) has failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.3.5 ERROR: sfcfsd: 0005: can't execute secondary MDS: mountpoint(mount_point)

[Explanation]

Start up of the secondary MDS for the file system (mount_point) has failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.3.6 ERROR: sfcfsd: 0006: can't take over MDS: mountpoint(mount_point)

[Explanation]

Switchover of the MDS for the file system (mount_point) failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.3.7 ERROR: sfcfsd: 0007: primary MDS down: mountpoint(mount_point)

[Explanation]

The primary MDS for the file system (mount_point) has failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.3.8 ERROR: sfcfsd: 0008: secondary MDS down: mountpoint(mount_point)

[Explanation]

The secondary MDS for the file system (mount_point) has failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.3.9 ERROR: sfcfsd: 0009: can't mount to primary MDS. gfs monitor daemon stop: mountpoint(mount_point)

[Explanation]

Mounting on the primary MDS for the file system (mount_point) failed. The GFS Shared File System monitoring daemon terminates.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.3.10 ERROR: sfcfsd: 0010: can't mount to secondary MDS: mountpoint(mount_point)

[Explanation]

Mounting on the secondary MDS for the file system (mount_point) failed.

[Action]

There is no problem with the operation of the file system. Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.3.11 ERROR: sfcfsd: 0011: blockade: mountpoint(mount_point)

[Explanation]

The file system (mountpoint) has been closed.

[Action]

The target mount point cannot be used and only unmounting can be performed. Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.4 sfcfs_mount command

This section explains the sfcfs_mount command messages that is called sfcfsd daemon.

E.3.2.4.1 ERROR: sfcfs_mount: 0001: mount_point: not superusr

[Explanation]

sfcfs_mount is not performed by super user.

[Action]

Do not execute the module directly.

E.3.2.4.2 ERROR: sfcfs_mount: 0002: block_special no such device

E.3.2.4.3 ERROR: sfcfs_mount: 0003: mount_point not a directory or a component of block_special is not a directory

E.3.2.4.4 ERROR: sfcfs_mount: 0004: block_special or mount_point, no such file or directory

E.3.2.4.5 ERROR: sfcfs_mount: 0005: block_special is not this fstype.

[Explanation]

Find setting error in the /etc/vfstab. Therefore, mount the file system will be failed.

[Action]

If AC has outputted the message just before this message, apply the countermeasures described in that message.

Correct the entry in /etc/vfstab. Moreover, try mount again.

E.3.2.4.6 ERROR: sfcfs_mount: 0006: block_special is already mounted, mount_point is busy, or the allowable number of mount points has been exceeded

[Explanation]

Some process is used mount_point or already mounted at mount_point. Therefore, mount the file system will be failed.

[Action]

Please check the process that is used mountpoint by fuser(1M). Or check the file system that is used mount_point by mount(1M).

E.3.2.4.7 ERROR: sfcfs_mount: 0007: block_special not a block device

[Explanation]

Find setting error in the /etc/vfstab. Therefore, mount the file system will be failed.

[Action]

Correct the entry in /etc/vfstab. Moreover, try mount again.

E.3.2.4.8 ERROR: sfcfs_mount: 0008: block_special write-protected

[Explanation]

block_special will be set write-protected Therefore, mount the file system will be failed.

[Action]

Change block_special setting to read and write mode.

E.3.2.4.9 ERROR: sfcfs_mount: 0010: large files may be present on block_special, and it was attempted to be mounted nolargefiles

[Explanation]

Files that have 2 gigabytes over size are included in the file system, when the mount option nolargefiles specified. Therefore, mount the file system will be failed.

[Action]

Change block_special setting to read and write mode.

E.3.2.4.10 ERROR: sfcfs_mount: 0011: mount_point: invalid argument

[Explanation]

Internal error occurred. Therefore, mount the file system will be failed.

[Action]

Please install same version level and same patch ID of GFS Shared File System in all nodes. If there are same, collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.4.11 ERROR: sfcfs_mount: 0013: mount_point: CFS protocol error

[Explanation]

Internal error occurred during communication with the meta-data server of mount_point. Therefore, mount the file system will be failed.

[Action]

Please install same version level and same patch ID of GFS Shared File System in all nodes. If there are same, collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.4.12 ERROR: sfcfs_mount: 0014: mount_point: response from MDS and information of AC are mismatch

[Explanation]

Internal error found in response from meta-data server. Therefore, mount the file system will be failed.

[Action]

Please install same version level and same patch ID of GFS Shared File System in all nodes. If there are same, collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.4.13 ERROR: sfcfs_mount: 0015: mount_point: cannot connect to Secondary-MDS

E.3.2.4.14 ERROR: sfcfs_mount: 0016: mount_point: cannot connect to Primary-MDS

[Explanation]

Access Client cannot connect to meta-data server. Therefore, mount the file system will be failed.

[Action]

Check meta-data server down. In this case, try mount again.

E.3.2.4.15 ERROR: sfcfs_mount: 0019: cannot mount block_special: errmsg [errno=no]

[Explanation]

Internal error occurred. Therefore, mount the file system will be failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.4.16 ERROR: sfcfs_mount: 0033: Cannot get port number of sfcfs-n for [P-MDS|S-MDS], not found in /etc/services

E.3.2.4.17 ERROR: sfcfs_mount: 0034: Cannot get port number sfcfs-n for [P-MDS|S-MDS], not found in /etc/services

[Explanation]

The port number sfcfs-n in /etc/services is not found. Therefore, mount the file system will be failed.

[Action]

Restore definition of sfcfs-n in /etc/services.

E.3.2.4.18 ERROR: sfcfs_mount: 0035: Length of host address z for host must be n

[Explanation]

Internal error occurred. Therefore, mount the file system will be failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.4.19 ERROR: sfcfs_mount: 0036: Cannot get host address of host for [P-MDS|S-MDS], not found in /etc/hosts

[Explanation]

Cannot get the host address of host. Therefore, mount the file system will be failed.

[Action]

Check host name (host) definition. Or change definition host name of the file system by sfcadm(1M).

E.3.2.5 sfcpncd daemon

E.3.2.5.1 ERROR: sfcpncd:0001: Permission denied. Abort.

[Explanation]

Execution was attempted with other than super user permission.

[Action]

Do not execute the module directly.

E.3.2.5.2 ERROR: sfcpncd:0002: Initialize fail. Abort.

[Explanation]

sfcpncd daemon failed booting.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.5.3 ERROR: sfcpncd:0003: Cannot create the semaphore. Abort.

[Explanation]

Creation of the semaphore failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.5.4 ERROR: sfcpncd:0004: Fatal error. Abort.

[Explanation]

sfcpncd daemon terminated abnormally.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.6 sfcprmd daemon

E.3.2.6.1 ERROR: sfcprmd:0001: Permission denied. Abort.

[Explanation]

Execution was attempted with other than super user permission.

[Action]

Do not execute the module directly.

E.3.2.6.2 ERROR: sfcprmd:0002: Initialize failed. Abort.

[Explanation]

sfcprmd daemon failed booting.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.6.3 ERROR: sfcprmd:0003: Cannot open /dev/null. Abort.

[Explanation]

Opening /dev/null failed.

[Action]

Check the system environment.

E.3.2.6.4 ERROR: sfcprmd:0004: Cannot access to the /var/opt/FJSVsfcfs/.sfcprmd_uds. Abort.

[Explanation]

Accessing /var/opt/FJSVsfcfs/.sfcprmd_uds failed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.6.5 ERROR: sfcprmd:0005: Memory not enough. Abort.

[Explanation]

There is insufficient memory to allow sfcprmd daemon to boot.

[Action]

Increase the swap space or the real memory.

E.3.2.6.6 ERROR: sfcprmd:0007: Cannot access to the semaphore of sfcpncd. Abort.

[Explanation]

The semaphore created by sfcpncd daemon cannot be accessed.

[Action]

Collect the diagnostic data with fjsnap and then contact local Customer Support.

E.3.2.7 sfcfsrm daemon

E.3.2.7.1 ERROR: sfcfsrm:0001: can not execute file_name

[Explanation]

file_name is not executable.

[Action]

See "PRIMECLUSTER (Solaris)Installation Guide." and reinstall the package

E.3.2.7.2 ERROR: sfcfsrm:0002: management_partition is not available

[Explanation]

The status of the GDS volume that was specified as the management partition is not ACTIVE. Alternatively, when exiting GFS, the user may have deleted a GDS volume without first using sfcsetup -d to delete node configuration information from the management partition in the target node.

[Action]

E.3.2.7.3 ERROR: sfcfsrm:0003: sfcfrmstart failed

[Explanation]

sfcfrmd daemon failed booting.

[Action]

Check the previous sfcfrmstart error message the was displayed on the console, then take action for that message according to the instructions in Appendix E.5.6, "sfcfrmstart command."

E.3.2.7.4 ERROR: sfcfsrm:0004: can not terminate daemon

[Explanation]

The daemon could not be stopped.

[Action]

Collect the diagnostic data with fjsnap and contact local Customer Support.

Contents Index PreviousNext
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004