From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: [pbs-devel] applied: [pve-devel] [PATCH ha-manager v3 0/6] watchdog-mux: sync log to disk before and after expiring
Date: Thu, 17 Jul 2025 18:00:16 +0200 [thread overview]
Message-ID: <175276796107.4120414.13175971172215069899.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250704133902.398663-1-m.sandoval@proxmox.com>
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
parent reply other threads:[~2025-07-17 16:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250704133902.398663-1-m.sandoval@proxmox.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175276796107.4120414.13175971172215069899.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox