[Info-vax] Quorum disk and last transition time

[Joe]

On Wednesday, January 28, 2015 at 5:46:52 PM UTC+1, Stephen Hoffman wrote:
> On 2015-01-28 15:49:31 +0000, Joe said:
> 
> If both voting hosts are present and accounted for, and both have one 
> vote each, and the quorum disk has one vote and there are three votes 
> total, no.   The quorum disk votes "matter" when there's not enough 
> non-quorum-disk votes present to meet quorum.  When the quorum disk 
> vote matters, there'll be pause of 3 x the polling interval, to ensure 
> there are no unrecognized hosts sharing access to the quorum disk.
> 

 Yes, your assumptions were correct. Thanks!!

> 
> If that's SCSI, then that's probably a flaky and failing quorum disk, 
> or a flaky and failing device somewhere else on the (presumably shared) 
> bus, maybe bus termination or a controller problem, or a bad or loose 
> cable.  If that's a Fibre Channel or DSSI bus involved, then adjust the 
> details accordingly.  In any case, investigate the devices and the 
> error logs for details, and expect to have to swap something.
> 

 Its a Fibre Channel disk.


> See above.  As for the logging, the system consoles are typically the 
> only "working" output devices during a quorum transition, and what 
> happens with the consoles is limited to output messages.   OPCOM and 
> other processes are intentionally wedged.  Any user-mode software and 
> any of the lower-priority kernel-mode VMS code is not going to be 
> stalled, pending the detection of quorum and the resumption of 
> processing.  That stall includes the ability to write to disk; there 
> won't be logging or other activity happening until after the stall is 
> cleared.

  Ok, thanks. As you have explained it didn't trigger state transition and nothing found on console in regards to transition at this time.

> I'd not be interested in the cluster state transitions, and would be 
> far more centrally interested in what's up with that quorum disk and 
> whatever bus is involved.
 
  Yes, we already identified the issue and working with the provider of storage. This is happening when the disk is served from a different site.

  Just got a little curious about how VMS clustering will work in this situation.
  Thanks, I got the answers :)