On 7/9/21 3:56 PM, Ulrich Windl wrote:
[...]
h19 kernel: Out of memory: Killed process 6838 (corosync) total-vm:261212kB,
anon-rss:31444kB, file-rss:7700kB, shmem-rss:121872kB
I doubt that was the best possible choice ;-)
The dead corosync caused the DC (h18) to fence h19 (which was
From: Users on behalf of Ulrich Windl
Sent: Friday, July 9, 2021 15:56
To: users@clusterlabs.org
Subject: [ClusterLabs] Antw: [EXT] Re: Antw: Hanging OCFS2 Filesystem any one
else?
Hi!
An update on the issue:
SUSE support found out that the reason
Hi!
An update on the issue:
SUSE support found out that the reason for the hanging processes is a deadlock
caused by a race condition (Kernel 5.3.18-24.64-default). Support is working on
a fix.
Today the cluster "fixed" the problem in an unusual way:
h19 kernel: Out of memory: Killed process
Hi Ulrich,
On 2021/6/15 17:01, Ulrich Windl wrote:
Hi Guys!
Just to keep you informed on the issue:
I was informed that I'm not the only one seeing this problem, and there seems
to be some "negative interference" between BtrFS reorganizing its extents
periodically and OCFS2 making reflink
Thanks for the update. Could it be something local to your environment ?
Have you checked mounting the OCFS2 on a vanilla system ?
Best Regards,Strahil Nikolov
On Tue, Jun 15, 2021 at 12:01, Ulrich
Windl wrote: Hi Guys!
Just to keep you informed on the issue:
I was informed that I'm not
Hi Guys!
Just to keep you informed on the issue:
I was informed that I'm not the only one seeing this problem, and there seems
to be some "negative interference" between BtrFS reorganizing its extents
periodically and OCFS2 making reflink snapshots (a local cron job here) in
current SUSE SLES
>>> Gang He schrieb am 02.06.2021 um 08:34 in Nachricht
> Hi Ulrich,
>
> The hang problem looks like a fix (90bd070aae6c4fb5d302f9c4b9c88be60c8197ec
> ocfs2: fix deadlock between setattr and dio_end_io_write), but it is not
100%
> sure.
> If possible, could you help to report a bug to SUSE,
