>>> Ken Gaillot schrieb am 01.03.2022 um 16:04 in
Nachricht
<463458e414f7c411eb1107335be6ee9a6e2d13ee.ca...@redhat.com>:
> On Tue, 2022‑03‑01 at 10:05 +0100, Ulrich Windl wrote:
>> Hi!
>>
>> For current SLES15 SP3 I noticed an oddity when the node running the
>> DC is going to be fenced:
>> It
On Tue, 2022-03-01 at 10:05 +0100, Ulrich Windl wrote:
> Hi!
>
> For current SLES15 SP3 I noticed an oddity when the node running the
> DC is going to be fenced:
> It seems that another node is performing recovery operations while
> the old DC is not confirmed to be fenced.
>
> Like this (116 is
>>> Klaus Wenninger schrieb am 01.03.2022 um 10:22 in
Nachricht
:
> On Tue, Mar 1, 2022 at 10:05 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
>> Hi!
>>
>> For current SLES15 SP3 I noticed an oddity when the node running the DC is
>> going to be fenced:
>> It seems that another
On Tue, Mar 1, 2022 at 10:05 AM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:
> Hi!
>
> For current SLES15 SP3 I noticed an oddity when the node running the DC is
> going to be fenced:
> It seems that another node is performing recovery operations while the old
> DC is not confirmed to
Hi!
For current SLES15 SP3 I noticed an oddity when the node running the DC is
going to be fenced:
It seems that another node is performing recovery operations while the old DC
is not confirmed to be fenced.
Like this (116 is the DC):
Mar 01 01:33:53 h18 corosync[6754]: [TOTEM ] A new
Hi!
I want to give an update on this issue (support is working on it):
First I recommend everyone using Xen and a Dell PowerEdge R7415 _not_ to
upgrade to SLES15 SP3, as we have about one crash per node and week.
We had one last night a few minutes after BtrFS balance had finished.
Meanwhile we
