[PATCH] Don't traceback if vg.teardown fails in recursive teardown.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It's possible that another lv in the same vg either has a
filesystem mounted or an active luks mapping, so just carry
on.
---
 storage/devices.py |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/storage/devices.py b/storage/devices.py
index ed997e8..f83b5b0 100644
--- a/storage/devices.py
+++ b/storage/devices.py
@@ -1795,7 +1795,13 @@ class LVMLogicalVolumeDevice(DMDevice):
             lvm.lvdeactivate(self.vg.name, self._name)
 
         if recursive:
-            self.vg.teardown(recursive=recursive)
+            # It's likely that teardown of a VG will fail due to other
+            # LVs being active (filesystems mounted, &c), so don't let
+            # it bring everything down.
+            try:
+                self.vg.teardown(recursive=recursive)
+            except Exception as e:
+                log.debug("vg %s teardown failed; continuing" % self.vg.name)
 
     def create(self, intf=None):
         """ Create the device. """
-- 
1.6.0.6

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux