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.
This series: - adds a second warning 10 seconds before the watchdog expires - syncs the journal to disk after the warning was issued - syncs the journal to disk after the watchdog expires The variable names in the second commit could use some feedback. The way the warning timeout is defined was arbitrary (10 seconds before the fence). Maximiliano Sandoval (3): watchdog: separate if in two parts watchdog: warn when about to expire watchdog: sync journal after sending expiration related messages src/watchdog-mux.c | 40 +++++++++++++++++++++++++++++++++------- 1 file changed, 33 insertions(+), 7 deletions(-) -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
