Veritas cluster node panicked after reservation conflict error messages

Issue

• The Veritas cluster node was panicked with following error messages in logs:

  sd 2:0:2:17: reservation conflict
  end_request: critical nexus error, dev sdfk, sector 64
  sd 2:0:2:17: reservation conflict
  end_request: critical nexus error, dev sdfk, sector 144
  sd 0:0:1:7: reservation conflict
  end_request: critical nexus error, dev sdai, sector 64
  sd 0:0:0:17: reservation conflict
  end_request: critical nexus error, dev sdr, sector 144
  sd 2:0:0:13: reservation conflict
  end_request: critical nexus error, dev sddh, sector 64
  Kernel panic - not syncing: GAB: Port h halting system due to client process failure at [14:1105]
  
  Pid: 0, comm: swapper Tainted: P        W  ---------------    2.6.32-358.18.1.el6.x86_64 #1
  Call Trace:
   <IRQ>  [<ffffffff8150da18>] ? panic+0xa7/0x16f
   [<ffffffffa0beeb33>] ? gab_halt+0x73/0x80 [gab]
   [<ffffffff81082134>] ? mod_timer+0x144/0x220
   [<ffffffffa0bef700>] ? gab_kill_process+0x180/0x370 [gab]
   [<ffffffff81012c09>] ? sched_clock+0x9/0x10
   [<ffffffffa0bef580>] ? gab_kill_process+0x0/0x370 [gab]
   [<ffffffffa0bdbd10>] ? gab_timerscan+0x0/0x540 [gab]
   [<ffffffffa0bdbe73>] ? gab_timerscan+0x163/0x540 [gab]
  [...]
  

  There were lots of reservation conflict error messages logged prior to the panic.