A.2.2.2 MDS(sfcfsmg) daemon

PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Linux)

Contents Index

Appendix A List of Messages

> A.2 GFS Shared File System Daemon messages

> A.2.2 Error messages

A.2.2.2 MDS(sfcfsmg) daemon

ERROR: sfcfs_mds:1001: MDS is failed.

[Explanation]

MDS failed in recovery mounting.

[Response]

Contact your local Customer Support.

ERROR: sfcfs_mds:1002: primary MDS is terminated.

[Explanation]

Primary MDS was terminated abnormally.

[Response]

Contact your local Customer Support.

ERROR: sfcfs_mds:1003: secondary MDS is terminated.

[Explanation]

Secondary MDS was terminated abnormally.

[Response]

Contact your local Customer Support.

ERROR: sfcfs_mds:1004: can't execute primary MDS

[Explanation]

Starting up primary MDS failed.

[Response]

Check following points.

Quantity of memory is enough.
- Check MemFree and SwapFree of /proc/meminfo.
State of a network is normal.
- Check whether DNS server is operating normally.
- Check whether connection of LAN is normal.
- Check whether network interface card is normal by ifconfig command.
Setting of network is normal.
- Check whether nodes sharing filesystem are described in /etc/hosts.
- Check whether IP address of a DNS server is described in /etc/resolv.conf.
- Check whether /etc/host.conf is described correctly.
- Check whether fire wall is set up correctly so that access of port used by GFS may not be refused.
State of volume of GDS is normal.
- Check state of volume of GDS by sdxinfo command. Refer to manual of GDS for details.
Isn't the disk breakdown?
- Confirm whether the error message of GDS or a disk driver is outputted to /var/log/messages. When the error message is outputted, please perform disposal corresponding to the message. Refer to the manual of GDS or disk units for details.
Is the file system configuration information normal?
- Please execute the following commands and check that the host name of the share node which the sfcinfo(8) command and the sfcrscinfo(8) command display and the host name specified to be -m option of the sfcadm(8) command execution line obtained by the sfcgetconf(8) command are the same.
  - sfcinfo -n <representative partition of the file system>
  
  - sfcrscinfo -m <representative partition of the file system>
  
  - sfcgetconf -d <representative partition of the file system> <output destination file name>
  
  When not the same, please perform the command line which changed into -u option -m option of the sfcadm(8) command execution line obtained by the sfcgetconf(8) command.

When unsolvable by the above methods, collect the diagnostic data with pclsnap, and contact your local Customer Support.

For details on above commands, see "sfcinfo(8)","sfcrscinfo(8)","sfcgetconf(8)" in this manual. Moreover for the details of the sfcadm(8) command execution line obtained by sfcgetconf(8), see "Backup and restore of the management partition information" in this manual.

ERROR: sfcfs_mds:1005: can't execute secondary MDS

[Explanation]

Starting up secondary MDS failed.

[Response]

Check following points.

Quantity of memory is enough.
- Check MemFree and SwapFree of /proc/meminfo.
State of a network is normal.
- Check whether DNS server is operating normally.
- Check whether connection of LAN is normal.
- Check whether network interface card is normal by ifconfig command.
Setting of network is normal.
- Check whether nodes sharing filesystem are described in /etc/hosts.
- Check whether IP address of a DNS server is described in /etc/resolv.conf.
- Check whether /etc/host.conf is described correctly.
- Check whether fire wall is set up correctly so that access of port used by GFS may not be refused.
State of volume of GDS is normal.
- Check state of volume of GDS by sdxinfo command. Refer to manual of GDS for details.
Isn't the disk breakdown?
- Confirm whether the error message of GDS or a disk driver is outputted to /var/log/messages. When the error message is outputted, please perform disposal corresponding to the message. Refer to the manual of GDS or disk units for details.
Is the file system configuration information normal?
- Please execute the following commands and check that the host name of the share node which the sfcinfo(8) command and the sfcrscinfo(8) command display and the host name specified to be -m option of the sfcadm(8) command execution line obtained by the sfcgetconf(8) command are the same.
  - sfcinfo -n <representative partition of the file system>
  
  - sfcrscinfo -m <representative partition of the file system>
  
  - sfcgetconf -d <representative partition of the file system> <output destination file name>
  
  When not the same, please perform the command line which changed into -u option -m option of the sfcadm(8) command execution line obtained by the sfcgetconf(8) command.

When unsolvable by the above methods, collect the diagnostic data with pclsnap, and contact your local Customer Support.

ERROR: sfcfs_mds:1006: can't execute MDS

[Explanation]

Starting up MDS failed.

[Response]

Contact your local Customer Support.

ERROR: sfcfs_mds:1007: MDS terminated because logreplay failed errcode = errcode

[Explanation]

The log replay by MDS of the file system failed.

[Response]

Contact your local Customer Support.

ERROR: sfcfs_mds:1008: fsid: Filesystem status is FSBAD, so MDS can not run. fs_clean = fs_clean

[Explanation]

Starting up MDS failed, because MDS detected a error in file system.

[Response]

Unmount the relevant file system from all of the nodes, and execute sfcfsck(8) specifying -o nolog.

ERROR: sfcfs_mds:1009: fsid: MDS terminated abnormally because I/O error occurred continuously on meta-data area of the disk.

[Explanation]

MDS terminated abnormally because I/O error occurred continuously on meta-data area of the disk.

[Response]

To resume the system operation, execute sfcfsck(8) in the full check mode first.

Then back up the file system and correct the hardware failure by replacing the failed disk with a new one, and restore the backed-up data to recover the file system.

Contents Index