Comment 1 for bug 1871874

Revision history for this message
Eric Desrochers (slashd) wrote : Re: lvmremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure

Curtin is currently using a two force:
$ lvremove --force --force vg_lv_name

as indicating here:
https://github.com/CanonicalLtd/curtin/blob/14c0560ed4482cb3b514fbec8d89118bd775652f/curtin/block/clear_holders.py#L136-L138

# LVREMOVE(8) #

Confirmation will be requested before deactivating any active LV prior to removal. LVs cannot be deactivated or removed while they are open (e.g. if they contain a mounted filesystem). Re‐moving an origin LV will also remove all dependent snapshots.

When a single force option is used, LVs are removed without confirmation, and the command will try to deactivate unused LVs.

To remove damaged LVs, two force options may be required (-ff).

-f|--force ...
Override various checks, confirmations and protections. Use with extreme caution.