** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1780196
Title:
Timed out Availability of block devi
I think it can be fixed in 2 ways:
* blkdeactivate handles properly the syncing software-raid arrays
* re-order this service, to be after the "standard" software-raid deinit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm
FYI: This problem can happen when the md0 device still synchronizing.
Now, when the md0 is in sync, the service stopped as well:
# journalctl -b -1 -u blk-availability.service
systemd[1]: Starting Availability of block devices...
systemd[1]: Started Availability of block devices.
systemd[1]: Stop
I found the commit where introduced this blkdeactivate:
https://sourceware.org/git/?p=lvm2.git;a=commit;h=c698ee14bbb1310cf2383c8977d14a8e29139f8c
> Traverses the tree of block devices and tries to deactivate them.
> Currently, it supports device-mapper-based devices together with LVM.
> See man/b
Public bug reported:
On a fresh Ubuntu 18.04 (64 bit) Server install, the blk-
availability.service always killed by timeout at shutdown.
I think the dependency of this service is bad, but I don't know what
would be the good shutdown order for this.
An almost same config has been worked on Xenia
5 matches
Mail list logo
