Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, What are disadvantages of disabling fencing It worked for me with fencing disabled, Now I still have access to my gfs2 partition when one node is unplugged I have only this in cluster.conf <?xml version="1.0"?> <cluster alias="cluster-setup" config_version="1" name="cluster-setup"> <rm log_level="4"/> <fence_daemon clean_start="1"/> <clusternodes> <clusternode name="node1" nodeid="1" votes="1"> <fence> </fence> </clusternode> <clusternode name="node2" nodeid="2" votes="1"> <fence> </fence> </clusternode> </clusternodes> <cman expected_votes="1" two_node="1"/> <dlm enable_fencing="0"/> </cluster> and this in drbd.conf global { usage-count yes; } common { syncer { rate 100M; } } resource res0 { protocol C; startup { wfc-timeout 20; degr-wfc-timeout 10; # we will keep this commented until tested successfully: become-primary-on both; } net { # the encryption part can be omitted when using a dedicated link for DRBD only: # cram-hmac-alg sha1; # shared-secret anysecrethere123; allow-two-primaries; } on node1 { device /dev/drbd0; disk /dev/sdb1; address 192.168.23.128:7789; meta-disk internal; } on node2 { device /dev/drbd0; disk /dev/sdb1; address 192.168.23.129:7789; meta-disk internal; } disk { fencing dont-care; } } but still I see messages in log trying to fence other node Oct 29 15:15:37 node1 corosync[1319]: [MAIN ] Completed service synchronization, ready to provide service. Oct 29 15:15:37 node1 kernel: dlm: closing connection to node 2 Oct 29 15:15:37 node1 fenced[1377]: fencing node node2 Oct 29 15:15:37 node1 fenced[1377]: fence node2 dev 0.0 agent none result: error no method Oct 29 15:15:37 node1 fenced[1377]: fence node2 failed Oct 29 15:15:40 node1 fenced[1377]: fencing node node2 Regards, Zohair Raza On Mon, Oct 29, 2012 at 7:08 PM, Felix Frank <ff at mpexnet.de> wrote: > Hi, > > On 10/29/2012 02:43 PM, Maurits van de Lande wrote: > > I think that adding the following option to the dlm section in > cluster.conf > > > > enable_fencing="0" > > > > might solve this problem. (but I have not tested this) This will disable > > fencing. > > ...but from what I remember from training and other threads here, it is > a Bad Idea to have a production dual-primary setup without fencing. > > Cheers, > Felix > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20121029/efa54aee/attachment.htm>