Disk space availability wrong after net-snmp update.
Andrea Venturoli
ml at netfence.it
Thu Aug 4 21:16:01 UTC 2011
Hello.
After the latest upgrade of net-snmp (5.7), Cacti displays wrong values
for available space (partition size is still correct).
This happens on different machines of mine with different arch and
version; I also heard other users having similar problems.
Where do I start debugging this? I'm willing to provide any additional
info or do testings.
As a sample, I'm pasting an snmpwalk output:
> HOST-RESOURCES-MIB::hrStorageDescr.31 = STRING: /
> HOST-RESOURCES-MIB::hrStorageDescr.32 = STRING: /dev
> HOST-RESOURCES-MIB::hrStorageDescr.33 = STRING: /usr
> HOST-RESOURCES-MIB::hrStorageDescr.34 = STRING: /var
> HOST-RESOURCES-MIB::hrStorageDescr.35 = STRING: /var/spool/imap
> HOST-RESOURCES-MIB::hrStorageDescr.36 = STRING: /data
> HOST-RESOURCES-MIB::hrStorageDescr.37 = STRING: /usr/local/local/backups
> HOST-RESOURCES-MIB::hrStorageDescr.38 = STRING: /var/named/dev
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = INTEGER: 4096 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.2 = INTEGER: 4096 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = INTEGER: 4096 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.6 = INTEGER: 1024 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.7 = INTEGER: 4096 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.8 = INTEGER: 4096 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.9 = INTEGER: 4096 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.10 = INTEGER: 4096 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.31 = INTEGER: 2048 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.32 = INTEGER: 512 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.33 = INTEGER: 2048 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.34 = INTEGER: 2048 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.35 = INTEGER: 2048 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.36 = INTEGER: 2048 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.37 = INTEGER: 2048 Bytes
> HOST-RESOURCES-MIB::hrStorageAllocationUnits.38 = INTEGER: 512 Bytes
> HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: 1555292
> HOST-RESOURCES-MIB::hrStorageSize.2 = INTEGER: 265152
> HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 270855306
> HOST-RESOURCES-MIB::hrStorageSize.6 = INTEGER: 632736
> HOST-RESOURCES-MIB::hrStorageSize.7 = INTEGER: 910197
> HOST-RESOURCES-MIB::hrStorageSize.8 = INTEGER: 30447
> HOST-RESOURCES-MIB::hrStorageSize.9 = INTEGER: 9816
> HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 4718560
> HOST-RESOURCES-MIB::hrStorageSize.31 = INTEGER: 2029031
> HOST-RESOURCES-MIB::hrStorageSize.32 = INTEGER: 2
> HOST-RESOURCES-MIB::hrStorageSize.33 = INTEGER: 50777075
> HOST-RESOURCES-MIB::hrStorageSize.34 = INTEGER: 76165633
> HOST-RESOURCES-MIB::hrStorageSize.35 = INTEGER: 253894418
> HOST-RESOURCES-MIB::hrStorageSize.36 = INTEGER: 245000335
> HOST-RESOURCES-MIB::hrStorageSize.37 = INTEGER: 1419033458
> HOST-RESOURCES-MIB::hrStorageSize.38 = INTEGER: 2
> HOST-RESOURCES-MIB::hrStorageUsed.1 = INTEGER: 1490224
> HOST-RESOURCES-MIB::hrStorageUsed.2 = INTEGER: 23789
> HOST-RESOURCES-MIB::hrStorageUsed.3 = INTEGER: 268467208
> HOST-RESOURCES-MIB::hrStorageUsed.6 = INTEGER: 632032
> HOST-RESOURCES-MIB::hrStorageUsed.7 = INTEGER: 892281
> HOST-RESOURCES-MIB::hrStorageUsed.8 = INTEGER: 5989
> HOST-RESOURCES-MIB::hrStorageUsed.9 = INTEGER: 849
> HOST-RESOURCES-MIB::hrStorageUsed.10 = INTEGER: 342914
> HOST-RESOURCES-MIB::hrStorageUsed.31 = INTEGER: 1500391
> HOST-RESOURCES-MIB::hrStorageUsed.32 = INTEGER: 0
> HOST-RESOURCES-MIB::hrStorageUsed.33 = INTEGER: 28549631
> HOST-RESOURCES-MIB::hrStorageUsed.34 = INTEGER: 19350682
> HOST-RESOURCES-MIB::hrStorageUsed.35 = INTEGER: 158375045
> HOST-RESOURCES-MIB::hrStorageUsed.36 = INTEGER: 169490522
> HOST-RESOURCES-MIB::hrStorageUsed.37 = INTEGER: 751038225
> HOST-RESOURCES-MIB::hrStorageUsed.38 = INTEGER: 0
I'm confused on how to interpret hrStorageUsed values; they should
correspond to:
> %df
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/mfid0s1a 4058062 1057280 2676138 28% /
> devfs 1 1 0 100% /dev
> /dev/mfid0s1d 101554150 44454888 48974930 48% /usr
> /dev/mfid0s1e 152331266 113629902 26514864 81% /var
> /dev/mfid0s1f 507788836 191038746 276126984 41% /var/spool/imap
> /dev/mfid0s1g 490000670 151019626 299780992 34% /data
> /dev/stripe/backup 2838066916 1335990466 1275031098 51% /usr/local/local/backups
> devfs 1 1 0 100% /var/named/dev
Are those figures wrong or is the problem elsewhere?
bye & Thanks
av.
More information about the freebsd-ports
mailing list