From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <aderumier@odiso.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id BE30B61E78 for <pve-devel@lists.proxmox.com>; Tue, 8 Sep 2020 09:11:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B17D412000 for <pve-devel@lists.proxmox.com>; Tue, 8 Sep 2020 09:11:23 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [89.248.211.110]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 3805911FF6 for <pve-devel@lists.proxmox.com>; Tue, 8 Sep 2020 09:11:23 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id A7FA018F44FB; Tue, 8 Sep 2020 09:11:22 +0200 (CEST) Received: from mailpro.odiso.net ([127.0.0.1]) by localhost (mailpro.odiso.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id eMEHfB1rVJ0y; Tue, 8 Sep 2020 09:11:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id 8E64618F44FC; Tue, 8 Sep 2020 09:11:22 +0200 (CEST) X-Virus-Scanned: amavisd-new at mailpro.odiso.com Received: from mailpro.odiso.net ([127.0.0.1]) by localhost (mailpro.odiso.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hxModi1YqlRg; Tue, 8 Sep 2020 09:11:22 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [10.1.31.111]) by mailpro.odiso.net (Postfix) with ESMTP id 7B2A518F44FB; Tue, 8 Sep 2020 09:11:22 +0200 (CEST) Date: Tue, 8 Sep 2020 09:11:22 +0200 (CEST) From: Alexandre DERUMIER <aderumier@odiso.com> To: dietmar <dietmar@proxmox.com> Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Message-ID: <1680829869.439013.1599549082330.JavaMail.zimbra@odiso.com> In-Reply-To: <1551800621.910.1599540071310@webmail.proxmox.com> References: <216436814.339545.1599142316781.JavaMail.zimbra@odiso.com> <1059698258.392627.1599381816979.JavaMail.zimbra@odiso.com> <508219973.775.1599394447359@webmail.proxmox.com> <1661182651.406890.1599463180810.JavaMail.zimbra@odiso.com> <72727125.827.1599466723564@webmail.proxmox.com> <1066029576.414316.1599471133463.JavaMail.zimbra@odiso.com> <872332597.423950.1599485006085.JavaMail.zimbra@odiso.com> <1551800621.910.1599540071310@webmail.proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailer: Zimbra 8.8.12_GA_3866 (ZimbraWebClient - GC83 (Linux)/8.8.12_GA_3844) Thread-Topic: corosync bug: cluster break after 1 node clean shutdown Thread-Index: 5ZCJgzX3Id8qbjnt4vGb7NoVgXis4A== X-SPAM-LEVEL: Spam detection results: 0 AWL 0.020 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] corosync bug: cluster break after 1 node clean shutdown X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Tue, 08 Sep 2020 07:11:23 -0000 >>It would really help if we can reproduce the bug somehow. Do you have and= idea how >>to trigger the bug? I really don't known. I'm currently trying to reproduce on the same cluster= , with softdog && noboot=3D1, and rebooting node. Maybe it's related with the number of vms, or the number of nodes, don't ha= ve any clue ... ----- Mail original ----- De: "dietmar" <dietmar@proxmox.com> =C3=80: "aderumier" <aderumier@odiso.com>, "Proxmox VE development discussi= on" <pve-devel@lists.proxmox.com> Envoy=C3=A9: Mardi 8 Septembre 2020 06:41:10 Objet: Re: [pve-devel] corosync bug: cluster break after 1 node clean shutd= own > I don't known too much how locks are working in pmxcfs, but when a corosy= nc member leave or join, and a new cluster memership is formed, could we ha= ve some lock lost or hang ?=20 It would really help if we can reproduce the bug somehow. Do you have and i= dea how=20 to trigger the bug?=20