accd99e7cd
Previously, loop devices for LVM volume groups backing files were not created after reboots, causing e.g. Cinder to fail with messages such as ERROR cinder.service [-] Manager for service cinder-volume devstack@lvmdriver-1 is reporting problems, not sending heartbeat. Service will appear "down". Now, we use systemd services to manage loop devices for backing files. Change-Id: I27ec027834966e44aa9a99999358f5b4debc43e0
17 lines
461 B
Plaintext
17 lines
461 B
Plaintext
[Unit]
|
|
Description=Activate LVM backing file %BACKING_FILE%
|
|
DefaultDependencies=no
|
|
After=systemd-udev-settle.service
|
|
Before=lvm2-activation-early.service
|
|
Wants=systemd-udev-settle.service
|
|
|
|
[Service]
|
|
ExecStart=/sbin/losetup --find --show %DIRECTIO% %BACKING_FILE%
|
|
ExecStop=/bin/sh -c '/sbin/losetup -d $$(/sbin/losetup --associated %BACKING_FILE% -O NAME -n)'
|
|
RemainAfterExit=yes
|
|
Type=oneshot
|
|
|
|
[Install]
|
|
WantedBy=local-fs.target
|
|
Also=systemd-udev-settle.service
|