Bug 635373 - virt-df should be robust against appliance crashes
virt-df should be robust against appliance crashes
Status: CLOSED UPSTREAM
Product: Virtualization Tools
Classification: Community
Component: libguestfs (Show other bugs)
unspecified
All Linux
low Severity medium
: ---
: ---
Assigned To: Richard W.M. Jones
:
Depends On: 635266
Blocks:
  Show dependency treegraph
 
Reported: 2010-09-19 06:12 EDT by Richard W.M. Jones
Modified: 2010-09-20 11:04 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 635266
Environment:
Last Closed: 2010-09-20 11:04:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Richard W.M. Jones 2010-09-19 06:12:21 EDT
+++ This bug was initially created as a clone of Bug #635266 +++

In the original bug report, the kernel problem causes
the appliance to crash.  This means virt-df cannot complete
the full scan of guests:

$ sudo virt-df -h
Filesystem                                Size       Used  Available  Use%
FedoraRawhidex64:/dev/sda1              484.2M      47.0M     412.2M   10%
FedoraRawhidex64:/dev/vg_f13x64/lv_root
                                          7.4G       2.8G       4.5G   39%
Minix3x32:/dev/sda5                      62.0M       5.3M      56.7M    9%
Minix3x32:/dev/sda6                     779.6M        60K     779.5M    1%
umount_all: call launch before using this function
(in guestfish, don't forget to use the 'run' command) at /usr/bin/virt-df line 353.

[there are more guests after this one]

virt-df should have a mode where it launches one
appliance per guest (as it used to do) which can be used
to work around this issue.

At the same time, reduce max drives to 25.

Note You need to log in before you can comment on or make changes to this bug.