Hi,
On 10/13/2016 04:27 PM, Ulrich Windl wrote:
So I'm wondering why it takes so long to finish the fencing process?
As I wrote: Using SBD this is paranoia (as fencing doesn't report back a status like
"completed" or "failed". Actually the fencing only needs a few seconds, but the
timeout is
If you want to reduce the multipath switching time, when one
controller goes down
https://www.redhat.com/archives/dm-devel/2009-April/msg00266.html
2016-10-13 10:27 GMT+02:00 Ulrich Windl :
Eric Ren schrieb am 13.10.2016 um 09:31 in Nachricht
> :
>> Hi,
>>
>> On 10/10/2016 10:46 PM, Ulrich W
>>> Eric Ren schrieb am 13.10.2016 um 09:31 in Nachricht
:
> Hi,
>
> On 10/10/2016 10:46 PM, Ulrich Windl wrote:
>> Hi!
>>
>> I observed an interesting thing: In a three node cluster (SLES11 SP4) with
> cLVM and OCFS2 on top, one node was fenced as the OCFS2 filesystem was
> somehow busy on unm
Hi,
On 10/11/2016 02:18 PM, Ulrich Windl wrote:
{ emmanuel segura schrieb am 10.10.2016 um 16:49 in
Nachricht
:
Node h01 (old DC) was fenced at Oct 10 10:06:33
Node h01 went down around Oct 10 10:06:37.
DLM noticed that on node h05:
Oct 10 10:06:44 h05 cluster-dlm[12063]: dlm_process_no
On Tue, Oct 11, 2016 at 9:18 AM, Ulrich Windl
wrote:
>
> My point is this: For a resource that can only exclusively run on one node,
> it's important that the other node is down before taking action. But for cLVM
> and OCFS2 the resources can run concurrently on each node,
Both require coordina
{ emmanuel segura schrieb am 10.10.2016 um 16:49 in
> Nachricht
> :
>
Node h01 (old DC) was fenced at Oct 10 10:06:33
Node h01 went down around Oct 10 10:06:37.
DLM noticed that on node h05:
Oct 10 10:06:44 h05 cluster-dlm[12063]: dlm_process_node: Removed inactive node
739512321: born-on=
