VCS CRITICAL V-16-1-1073 DiskGroup:xxxx:monitor:Disk Group: xxxx is disabled on system: xxx. System will panic to migrate all service groups to another VCS node

Article: 100026592
Last Published: 2023-10-29
Ratings: 18 0
Product(s): InfoScale & Storage Foundation

Problem

When one data dg is disabled , the SG is failover and this node is panic.

Error Message

Mar 12 15:00:58 g4cs1010 Had[54]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-1073 (g4cs1010) DiskGroup:DG_databak_data:monitor:Disk Group: dghq_databak_data is disabled on system: g4cs1010. System will panic to migrate all service groups to another VCS node in system list

Cause

The DiskGroup agent has a function named PanicSystemOnDGLOSS. this function serves to move the service group from the faulty node to a working node should the DiskGroup become disabled or otherwise unresponsive. the machine is panicked to preserve data integrity and to allow the diskgroup to be removed from the system that is having the issue. This allows the service group to migrate to a working host.

 

Solution

Change the resource attribute :
open configuration file:
#haconf -makerw   
next modify the attribute:
#hares -modify <DG resource> PanicSystemOnDGLoss <value>
next, close the configuration:
#haconf -dump -makero
 
Or
manually edit types.cf:
#hastop -all -force
edit file on one node:
#vi /etc/VRTSvcs/conf/config/types.cf
...
PanicSystemOnDGLos=0
...
start had on all cluster nodes:
#hastart
 

This attribute accepts the following values:

  • 0: Do not halt the system

  • 1: halt the system if either disk group goes into disabled state or the disk group resource faults due to monitor timeout

  • 2: halt the system only if disk group goes into disabled state

  • 3: halt the system only if disk group resource faults due to monitor timeout

Was this content helpful?