Comment 8 for bug 1270192

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to cinder (master)

Reviewed: https://review.openstack.org/99784
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=da9597aed0186e68dbf1c7304b30e49f8e6a54ff
Submitter: Jenkins
Branch: master

commit da9597aed0186e68dbf1c7304b30e49f8e6a54ff
Author: Dirk Mueller <email address hidden>
Date: Fri Jun 13 00:24:23 2014 +0200

    Retry lvremove with ignore_suspended_devices

    A lvremove -f might leave behind suspended devices
    when it is racing with udev or other processes
    still accessing any of the device files. The previous
    solution of using lvchange -an on the LV had the
    side-effect of deactivating origin LVs alongway in
    the thick volume case, which was undesired.

    It turns out retrying the deactivation twice and
    ignoring the suspended devices on the second iteration
    avoids the hang of all LVM operations after an initial
    failure.

    Change-Id: I0d6fb74084d049ea184e68f2dcc4e74f400b7dbd
    Closes-Bug: #1317075
    Related-Bug: #1270192