lvm2-lvmlocking.service incorrectly uses nonexistent option --lock-opt autowait
Bug #1874142 reported by
WGH
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The lvm2-lvmlocking
# start lockspaces and wait for them to finish starting
ExecStart=
This is unfortunately wrong: the autowait option was dropped in this commit: https:/
It should've said --lock-opt auto.
To post a comment you must log in.
https:/ /www.redhat. com/archives/ lvm-devel/ 2020-April/ msg00017. html fixed upstream, but still affects both Ubuntu 18.04 and 20.04 (/lib/systemd/ system/ lvm2-lvmlocking .service and /lib/systemd/ system/ lvmlocks. service correspondingly)