Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 140687 - Logwatch doesn't generate correct disk space output when using lvm
Logwatch doesn't generate correct disk space output when using lvm
Status: CLOSED DUPLICATE of bug 138285
Product: Fedora
Classification: Fedora
Component: logwatch (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jiri Ryska
Depends On:
  Show dependency treegraph
Reported: 2004-11-24 03:52 EST by Holger Eilhard
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:07:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Holger Eilhard 2004-11-24 03:52:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5)
Gecko/20041108 Firefox/1.0

Description of problem:
I'm running LVM on my machine and I only get this output:

/dev/sda1              97M   12M   80M  14% /boot

instead of:

                       15G  3,8G   11G  27% /
/dev/sda1              97M   12M   80M  14% /boot
                      139G   69G   66G  52% /LogVolData

This is likely due to the call "df -h | grep '^/dev/'" in
/etc/log.d/scripts/services/zz-disk_space which creates the first
output. Because of the line break after the device name, the actual
size is not shown.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a volume group
2. wait for the first logwatch run

Additional info:
Comment 1 Jiri Ryska 2004-11-24 06:50:15 EST

*** This bug has been marked as a duplicate of 138285 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:07:15 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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