PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Solaris(TM) 10 Operating System)

A.2.4 Error messages (MDS (sfcfsmg daemon))

This section explains the MDS (sfcfsmg daemon) error messages of the GFS Shared File System.

---

 

ERROR: sfcfs_mds:0001: v_count != 0 inode = ino_pointer ino = ino_num

[Explanation]

An error was detected in releasing the i-node (ino_num) in the file system.

[Response]

Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.

---

 

ERROR: sfcfs_mds:1001: MDS is failed

[Explanation]

MDS failed in recovery mounting.

[Response]

Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.

---

 

ERROR: sfcfs_mds:1002: primary MDS is terminated

[Explanation]

Primary MDS was terminated abnormally.

[Response]

Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.

---

 

ERROR: sfcfs_mds:1003: secondary MDS is terminated

[Explanation]

Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.

[Response]

Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.

---

 

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

[Explanation]

Startup of the primary MDS or secondary MDS failed.

[Response]

Check following points.

• Quantity of memory is enough.
  • Check if a message indicating insufficient memory of Solaris OS is output to the console.
• 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(1M).
• 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/nsswitch.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. For details on sdxinfo, see "Appendix D.6 sdxinfo" of the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide (Solaris(TM) Operating System)".
• Isn't the disk breakdown?
  • Confirm whether the error message of GDS or a disk driver is outputted to /var/adm/messages. When the error message is outputted, please perform disposal corresponding to the message. For details, see "PRIMECLUSTER Global Disk Services Configuration and Administration Guide (Solaris(TM) Operating System)" or the manual of disk units.
• 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(1M) command and the sfcrscinfo(1M) command display and the host name specified to be -m option of the sfcadm(1M) command execution line obtained by the sfcgetconf(1M) 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(1M) command execution line obtained by the sfcgetconf(1M) command.

When unsolvable by the above methods, collect the diagnostic data with fjsnap, and contact your local Customer Support.
For details on above commands, see sfcinfo(1M), sfcrscinfo(1M), sfcgetconf(1M).Moreover for the details of the sfcadm(1M) command execution line obtained by sfcgetconf(1M), see "9.6 Backup of the management partition information" and "9.7 Restoring of the management partition information".

---

 

ERROR: sfcfs_mds:1006: can't execute MDS

[Explanation]

Starting up MDS failed.

[Response]

Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.

---

 

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

[Explanation]

The log replay by MDS of the file system failed.

[Response]

Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.

---

 

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 fsck_sfcfs(1M) 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 fsck_sfcfs(1M) 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.