Hi all,
Just to caution you when you are using my config, upgrading from PVE8 -> PVE9 it will reset (atleast on my end) the added definitions in the systemd unitfile for lvmlockd.
They were erased/reset to default.
So this in essence the timing-issues as mentioned in the beginning of this thread got re-introduced.
Effect seen : all nodes will join the global lockspace, but not the volume-lockspaces.
Howto solve:
Re-define the introduced parameters in the systemd -file:
...And afterwards reboot the nodes
- Glowsome
Just to caution you when you are using my config, upgrading from PVE8 -> PVE9 it will reset (atleast on my end) the added definitions in the systemd unitfile for lvmlockd.
They were erased/reset to default.
So this in essence the timing-issues as mentioned in the beginning of this thread got re-introduced.
Effect seen : all nodes will join the global lockspace, but not the volume-lockspaces.
Howto solve:
Re-define the introduced parameters in the systemd -file:
Code:
[Unit]
Description=LVM lock daemon
Documentation=man:lvmlockd(8)
After=corosync.service dlm.service # needed for correct operation/timing
[Service]
Type=notify
ExecStartPre=/bin/sleep 20 # ensures timing on lockspaces
ExecStart=/sbin/lvmlockd --foreground
PIDFile=/run/lvmlockd.pid
SendSIGKILL=no
[Install]
WantedBy=multi-user.target...And afterwards reboot the nodes
- Glowsome
Last edited:
