Hi vlad,

There is the localonly flag on the devices which you can set to avoid 
them being fenced.
With QFS, this configuration is explicitly supported and documented. I 
presume
you have looked at the appropriate documentation at:

http://docs.sun.com/source/819-7935-10/chapter6.html#94364

in the section titled "Configuring Shared Clients Outside the Cluster"?

If not, take a look and post here if it still doesn't answer your question.

HTH,
-ashu


vlad f halilov wrote:
> Hi there. Is any way to prevent device from reservation during fencing? I 
> have an shared qfs in cluster wnvironment and some clients outside a cluster. 
> When one node going down, second own all available device include qfs shared 
> target, that must always available to client. After that, clients stop 
> accessing qfs with reservation conflict message and i got halted network. I 
> not found any methods to stop fencing for specified device, so just remove it 
> from did_instances with checksum correction. This cause some small bug, but 
> cluster still operational. Any idea how to do it correctly?
> --
> 
> This message posted from opensolaris.org
> 
> _______________________________________________
> ha-clusters-discuss mailing list
> ha-clusters-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/ha-clusters-discuss

Reply via email to