I'm not sure what you're asking here, but it sounds like you're describing a qdisk. If a node loses heartbeat with the rest of the cluster, that's a fencin'. Doesn't matter if it can still access the shared storage, and if it has lost communication with the rest of the cluster, you probably don't want it accessing your data anyway. <div class="gmail_quote">On Fri, Jul 17, 2009 at 9:20 AM, James Devine <<a href="mailto:fxmulder@gmail.com">fxmulder@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Has anybody looked into using the network for heartbeat only, and disk for fencing in GFS? i.e. using the disk to communicate quorum when network heartbeat is lost between 1 or more nodes. If the disk is still accessible to all nodes, this should be a valid way to communicate quorum, if not, then the remaining nodes, assuming enough for quorum, should be able to continue knowing that nodes it can't communicate with either have been fenced or can't read/write to disk anyway. Does this sound like a valid approach? -- Linux-cluster mailing list <a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/linux-cluster" target="_blank">https://www.redhat.com/mailman/listinfo/linux-cluster</a> </blockquote></div>