Hi,
I am running a 4 node cluster with a multipathed quorum disk, configured to use the path /dev/dm-1. The problem that I am having is that if I lose one path to the disk (am testing by pulling one fibre), the node is almost always fenced (one node, once, managed to stay up, out of more than 10 attempts). Is there some timeout that needs changing to give qdiskd the time to realise that a path is down? I have tried an interval of 3 seconds with at TKO of 10, with no success, and a token timeout set at 45000ms:
<totem consensus="4800" join="60" token="45000" token_retransmits_before_loss_const="20"/>
<quorumd device="/dev/dm-1" interval="3" min_score="1" tko="10" votes="3"/>
output of mkqdisk -L:
[root@host3 ~]# mkqdisk -L
mkqdisk v0.5.1
/dev/sdc1:
Magic: eb7a62c2
Label: cms_qdisk
Created: Mon May 26 14:24:29 2008
Host: host3
/dev/sdd1:
Magic: eb7a62c2
Label: cms_qdisk
Created: Mon May 26 14:24:29 2008
Host: host3
/dev/dm-1:
Magic: eb7a62c2
Label: cms_qdisk
Created: Mon May 26 14:24:29 2008
Host: host3
When the node subsequently boots, with only one path, everything works just fine, so it can obviously use both paths.
Is anyone able to offer any advice on why this is happening (and how to stop it)?
Regards,
Darrin.
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster