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

F.1.6 Cluster System Related Error

---

 

(1) The PRIMECLUSTER CF clinitreset(1M) command ends abnormally outputting an error message # 6675.

 

[Explanation]

When a class exists in a cluster system, initializing the PRIMECLUSTER resource database with the PRIMECLUSTER CF clinitreset command results in that the clinitreset command fails outputting the following error message.

FJSVcluster: ERROR: clinitreset: 6675: Cannot run this command
because Global Disk Services has already been set up.

When a node containing a shadow class is rebooted because of an event such as shutdown and panic, the shadow class is deleted, but the /dev/sfdsk/Class Name directory is not deleted. If the clinitreset command is executed here, the command also fails outputting the error message as above.

 

[Resolution]

1. On all nodes in the cluster system, view the configuration of objects and delete a class if any exists. If a class is deleted, volume data will be lost. If necessary, back up volume data in advance.

   
   For using GDS Management View, see "Removals."
   
   
   For using commands, see "Command Reference."
   

2. On all nodes in the cluster system, check whether a class directory exists in the /dev/sfdsk directory, and delete a class directory if any exists. The following shows an example when a directory of class Class1 exists.

   _adm and _diag are special files used by GDS and cannot be deleted.

   # cd /dev/sfdsk
   # ls
   _adm _diag Class1
   # rm -rf Class1

    

 

---

 

(2) Cluster applications become "Inconsistent".

 

[Explanation]

If a shared class is not to be used as an RMS resource, volumes included in the class are started on node startup. If a cluster application that uses those volumes are started there, the cluster application becomes "Inconsistent" because the volumes are already active. By default, classes are not to be used as RMS resources. Classes can be made available as RMS resources either by:

• Registering them in resources used by cluster applications through the Web-Based Admin View's userApplication Configuration Wizard
• Specifying them and using the hvgdsetup -a command

   

[Resolution]

Make the shared class available as an RMS resource with one of the following methods. After performing the procedures, restart the cluster application.

• If the class is not registered in resources used by the cluster application, register it through the userApplication Configuration Wizard.
• If the class is already registered in resources used by the cluster application, execute the following command.

  # /usr/opt/reliant/bin/hvgdsetup -a Class Name
  ~

  Do you want to continue with these processes ? y

   

---

 

(3) The GFS Shared File System is not mounted on node startup.

 

[Explanation]

If a shared class is to be used as an RMS resource, volumes included in the class are not started on node startup. Therefore, the GFS Shared File System on those volumes is not mounted on node startup. By default, classes are not to be used as RMS resources, but they are made available as RMS resources either by:

• Registering them in resources used by cluster applications through the Web-Based Admin View's userApplication Configuration Wizard
• Specifying them and using the hvgdsetup -a command

   

[Resolution]

Take one of the following actions.

a) When using the shared class as an RMS resource, do not create the GFS Shared File System on volumes in the class, but create it on volumes in a difference class.
b) When not using the shared class as an RMS resource, make the class unavailable as an RMS resource again with one of the following methods. After performing the procedures, reboot the system.

• If the class is registered in resources used by the cluster application, remove it through the userApplication Configuration Wizard.
• If the class is not registered in resources used by the cluster application, execute the following command.

  # /usr/opt/reliant/bin/hvgdsetup -d Class Name
  ~
  Do you want to continue with these processes ? y
  ~

  Do you need to start volumes in the specified disk class ? n