. Setting the VG to non-clustered
might fix the problem. If clustered is intended, you must start the cLVM framework.
Regards,
Ulrich
Craig Lesle craig.le...@bruden.com schrieb am 24.07.2013 um 21:19 in
Nachricht 51f028bc.8030...@bruden.com:
Thought I would start here to report a clvm/dlm issue
Thought I would start here to report a clvm/dlm issue. If this is the
wrong place for this inquiry, please let me know - thank you.
Upgraded a pacemaker two node HA configuration from openSUSE 12.2 to
12.3. Previously the 12.2 configuration has been running fine for
several months.
Am
... right. I hadn't noticed that before.
So what's happening is that, in pacemaker's fencing/remote.c, the
stonith-timeout specified is divided up in 10% for _querying_ the list
of nodes a given stonith device can retrieve, and 90% for then
performing an actual operation. (Compare
Hi Lars,
/ Timeout (msgwait) : 90
// stonith-timeout=100s \
/
You may want to increase stonith-timeout a bit further, to increase the
difference between msgwait (the time that sbd will wait before
returning) and the cluster allowed time for that. But 10s should not be
too little,
Greetings.
Let me set up the scene. Two node cluster, SUSE11 SP1 updated/patched as
of 7/1/2011.
The sbd device and timeout values used are as follows.
capep01:~ # sbd -d
/dev/disk/by-id/scsi-36001438005de94646747 dump
==Dumping header on disk
