Common cause of that error is udev running stuff that opens and accesses the device while lvm2 is trying to remove it. Fix the udev rules so there's no attempt to open those devices.
Long-term fix needs a new userspace notification mechanism: udev will notify lvm2 when it's finished whatever it's doing, and lvm2 will wait for that notification before proceeding. Also udev must totally ignore 'add' events from device-mapper devices and act instead on the 'change' events we added upstream recently. ['add' event is triggered in the kernel when the device number is reserved and the device is not yet usable - there are intrinsic races; 'change' is triggered when the device is ready for use incl. each time its constitution changes and udev ought to reprocess it.] Alasdair -- [EMAIL PROTECTED] -- [feisty] failures when creating snapshots "in use: not deactivating" https://launchpad.net/bugs/84672 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
