Bug#734794: (no subject)

[Patrick Schleizer]

> From: Ritesh Raj Sarraf <rrs at debian.org>
> On 12/02/2014 07:04 PM, Sebastian Pipping wrote:
>> I can confirm that kpartx needs "sleep 2" /after/ adding or removing
>> partitions before running some other command that assumes the
>> partitions are now gone (or in place).  My guess is that something
>> needs to propagate and kpartx could either wait for that change to
>> happen before quitting or not, and the current code does not.
>>
> 
> When you add/remove *partitions*, yes. That's understood.

Can you please elaborate on this?

What would be the right course of action, so we don't have to hardcode
"sleep 2"? Is there any command that would wait until kpartx is ready?
Or that would tell us whether it's safe now or not to use kpartx?

Cheers,
Patrick