Bug 144012

Summary: disk usage output split with long filesystem name
Product: Red Hat Enterprise Linux 4 Reporter: Joshua Daniel Franklin <joshuadfranklin>
Component: logwatchAssignee: Jiri Ryska <jryska>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-11 15:21:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Joshua Daniel Franklin 2005-01-03 19:18:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
As reported in bug #142863, the default naming scheme of
/dev/mapper/VolGroup00-XXX filesystem names are too long for normal df
output. The logwatch file /etc/log.d/scripts/services/zz-disk_space 
should use the -P flag to get useful output. 

Currently LogWatch (on by default in RHEL4b2) shows nearly useless
output like this:

------------------ Disk Space --------------------

/dev/mapper/VolGroup00-RootVol00
/dev/sda1              99M   32M   63M  34% /boot
/dev/mapper/VolGroup00-HomeVol02
/dev/mapper/VolGroup00-LocalVol04
/dev/mapper/VolGroup00-VarVol03


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

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL3b2 with default filesystem names
2. Run LogWatch
3. Look at output
    

Additional info:

Comment 1 Joshua Daniel Franklin 2005-03-01 22:16:38 UTC
An alternative way of fixing this would be to make the default
anaconda naming scheme something like 'vg0x' and 'lv0x' instead of
'VolGroup0x' and 'LogVol0x'. This would also be a mnemonic to connect
the volume with the tools used with them (vgdisplay, etc.)

Comment 2 Jiri Ryska 2005-04-11 15:21:39 UTC

*** This bug has been marked as a duplicate of 152419 ***