Archived community.zenoss.org | full text search
Skip navigation
30735 Views 2 Replies Latest reply: Dec 15, 2009 4:23 AM by chitambira RSS
seunaw Rank: White Belt 9 posts since
Sep 4, 2009
Currently Being Moderated

Dec 14, 2009 2:56 PM

Incorrect Disk Usage Data

I am running into an issue when monitoring disk space on a centos 5 machine, on the cli after running the df command I get the following:

 

[tracking1] ~ # df -H
Filesystem                                        Size   Used  Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00       2.0T   1.8T    67G  97% /
/dev/sda1                                        104M    12M    87M  12% /boot
tmpfs                                                 4.3G      0   4.3G   0% /dev/shm

 

But SNMP/Zenoss reports

 

             
Mount Total bytes Used bytes Free bytes % Util M Lock
/1.7TB1.6TB154.4GB91
/boot98.7MB10.7MB88.0MB10

 

Is this just me or is someone else seeing inconsistent data also.

 

 

Thanks in advance.

  • guyverix ZenossMaster 846 posts since
    Jul 10, 2007
    Currently Being Moderated
    1. Dec 14, 2009 8:48 PM (in response to seunaw)
    Re: Incorrect Disk Usage Data
    I have seen that too.  Try to walk the snmp tree for disk use, and I suspect you will find that Zenoss is using the values that SNMP is giving it.  The differences are probably due to the way net-snmp is looking at your disk use compared to the way df -h reports it.  I would bet both are actually accurate depending on your point of view.
  • chitambira Rank: Brown Belt 711 posts since
    Oct 15, 2008
    Currently Being Moderated
    2. Dec 15, 2009 4:23 AM (in response to guyverix)
    Re: Incorrect Disk Usage Data

    This is a known issue. Linux ext2/3 file systems reserve some 5% of the file system for the root user in case it all fills up, otherwise denying everyone access.

    This space is hidden from df, but not to snmp. It is a matter of choice on how to approach this. There are two ways.

    1)Remove this reservation in your filesystems. ~]# tune2fs -m 0 /mount/point

    2)Take the offset into consideration in zenoss, follow this doc; docs/DOC-3233

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points