* Srinivasa Ds <srinivasa@in.ibm.com> wrote: > On debugging I found out that,"dmsetup suspend <device name>" calls > "freeze_bdev()",which locks "bd_mount_mutex" to make sure that no new > mounts happen on bdev until thaw_bdev() is called. > This "thaw_bdev()" is getting called when we resume the device > through "dmsetup resume <device-name>". > Hence we have 2 processes,one of which locks > "bd_mount_mutex"(dmsetup suspend) and Another(dmsetup resume) unlocks > it. hm, to me this seems quite a fragile construct - even if the mutex-debugging warning is worked around by reverting to a semaphore. Ingo _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
