From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 6FF061FF165 for ; Thu, 17 Jul 2025 18:00:07 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4E2E53FF0A; Thu, 17 Jul 2025 18:00:59 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com, Maximiliano Sandoval Date: Thu, 17 Jul 2025 18:00:16 +0200 Message-ID: <175276796107.4120414.13175971172215069899.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250704133902.398663-1-m.sandoval@proxmox.com> References: <20250704133902.398663-1-m.sandoval@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1752768022667 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.032 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] applied: [pve-devel] [PATCH ha-manager v3 0/6] watchdog-mux: sync log to disk before and after expiring X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" On Fri, 04 Jul 2025 15:38:56 +0200, Maximiliano Sandoval wrote: > Without a clear-cut message in the log, it is very hard to provide a definitive > answer to whether a host fenced or not. In some cases the journal on the disk > can be missing up to 2 minutes since its last logged entry and the time where > another node detects the corosync link is down, with such a gap, the fenced node > would not even record that it lost conenction and it is not possible to > fully-determine if the node was fenced or not. > > [...] Applied, thanks! [1/6] watchdog-mux: Use #define for 60s timeout [2/6] watchdog-mux: split if block in two if blocks [3/6] watchdog-mux: warn when about to expire [4/6] watchdog-mux: sync journal right after fence warning [5/6] watchdog-mux: break out of loop when updates are disabled [6/6] watchdog-mux: Remove wrapping if guard _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel