Bug#946882: blk-availability.service: may fail or unmount filesystems too soon

2021-02-05 Thread Ivo De Decker
Control: tags -1 patch Control: retitle -1 blkdeactive hardcodes wrong path to sort On Mon, Dec 16, 2019 at 04:38:45PM -0800, Rob Leslie wrote: > On systems upgraded from stretch and without the usrmerge package installed, > /sbin/blkdeactivate (ExecStop= of blk-availability.service) gives the >

Bug#946882: blk-availability.service: may fail or unmount filesystems too soon

2020-08-03 Thread Antonio
I don't know if it's relevant, but I'm getting this a warning at boot with this service: systemd[1]: /lib/systemd/system/blk-availability.service:10: Neither a valid executable name nor an absolute path: ${exec_prefix}/bin/true lvm2/2.03.09-2

Bug#946882: blk-availability.service: may fail or unmount filesystems too soon

2019-12-16 Thread Rob Leslie
Package: lvm2 Version: 2.03.02-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, On systems upgraded from stretch and without the usrmerge package installed, /sbin/blkdeactivate (ExecStop= of blk-availability.service) gives the following error during system shutdown: