Dear Maintainers, I kindly ask you to restore the init scripts removed in the commit "Remove remaining unused init scripts". [1] I can report that they both are still in use and work fine except for bug #989345 [2] which has a patch available. Thanks for your work, Valentin [1] https://salsa.debian.org/lvm-team/lvm2/-/commit/361969e6035ca57f584c06f348281e3e27d48351 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989345
Please describe your real problems. I verified that a not running lvmpolld is not a problem and only outputs a warning: | /run/lvm/lvmpolld.socket: connect failed: Connection refused | WARNING: Failed to connect to lvmpolld. Proceeding with polling without using lvmpolld. | WARNING: Check global/use_lvmpolld in lvm.conf or the lvmpolld daemon state. And udev does a pretty good job in enabling LV when they become available. Bastian
Hi, not running: For setups with lvmlockd enabled pvmove will fail. Tested on our cluster: |root@olympic:~# pvmove /dev/drbd0 -n test_pvmove /dev/drbd1 | /run/lvm/lvmpolld.socket: connect failed: No such file or directory | WARNING: Failed to connect to lvmpolld. Proceeding with polling without using lvmpolld. | WARNING: Check global/use_lvmpolld in lvm.conf or the lvmpolld daemon state. | Enable lvmpolld when using lvmlockd. |root@olympic:~# echo $? |5 See also the corresponding code at https://sourceware.org/git/?p=lvm2.git;a=blob;f=tools/pvmove.c;hb=HEAD#l835 required. Valentin PS: we do have init scripts for lvmlockd which we'd gladly share if you'd like to increase its compatibility with sysvinit