Bug#734794: (no subject)

Patrick Schleizer adrelanos at riseup.net
Sun Jun 7 14:36:50 UTC 2015

Does upstream know about this issue?

What would be the real fix to solve this timing problem?

Are there commands, such as:

- 'kpartx --wait-until-ready' that waits as long as required or,

- 'kpartx --is-ready' that exits 0 or 1 accordingly.

Or would implementing those up to 'kpartx' or another project?


More information about the pkg-lvm-maintainers mailing list