Thanks Lar for reply, > The SBD mechanism provides a way to fence errant nodes. The cluster > manager itself ensures that it does not activate the resource several > times.
my concern is suppose SBD resource is running on say node1 even then node2 who is member of cluster will be able to access SBD device. or i think a node who is not even member of cluster will be able to access the SBD device. SBD does not provide exclusive access. am i wrong. other most important thing for me is, does scsi2reservation calls sg_persist in background?? or can we configure it to do so some how. please do confirm. > > > > Mit freundlichen Grüßen, > Lars > > -- > Teamlead Kernel, SuSE Labs, Research and Development > SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker >
_______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
