Bug 748410 – hrStorageSize from HOST-RESOURCES-TYPES mib reports incorrect size for filesystems > 16TB

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 748410 - hrStorageSize from HOST-RESOURCES-TYPES mib reports incorrect size for filesystems > 16TB

Summary:	hrStorageSize from HOST-RESOURCES-TYPES mib reports incorrect size for filesy...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	net-snmp (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	x86_64 Linux

Priority	low Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Jan Safranek
QA Contact:	Dalibor Pospíšil
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	654384
Blocks:	741789
	Show dependency tree / graph

Reported:	2011-10-24 07:49 EDT by Jan Safranek
Modified:	2013-09-05 11:34 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Previously, the snmpd daemon strictly implemented RFC 2780. However, this specification no longer scales well with modern big storage devices with small allocation units, and consequently, snmpd reported a wrong value of the HOST-RESOURCES-MIB::hrStorageSize object when working with a large file system (larger than 16TB), because the accurate value would not fit into Integer32 as specified in the RFC. To address this issue, this update adds a new option to the /etc/snmp/snmpd.conf configuration file, realStorageUnits. By changing the value of this option to 0, users can now enable recalculating all values in hrStorageTable to ensure that the multiplication of hrStorageSize and hrStorageAllocationUnits always produces an accurate device size. On the other hand, the values of hrStorageAllocationUnits are artificial and do not represent the real size of the allocation unit on the storage device.
Story Points:	---
Clone Of:	654384
Environment:
Last Closed:	2012-06-20 03:21:47 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	42345	None	None	None	Never
Red Hat Product Errata	RHSA-2012:0876	normal	SHIPPED_LIVE	Moderate: net-snmp security and bug fix update	2012-06-19 15:28:47 EDT

Groups: None (edit)

Comment 2 Jan Safranek 2012-02-06 09:23:46 EST

Note to QA: please test *very* carefully hrStorageTable, hrFSTable and hrDiskTable.

Comment 3 Jan Safranek 2012-02-06 09:23:46 EST

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the snmpd daemon strictly implemented RFC 2780. However, this specification no longer scales well with modern big storage devices with small allocation units, and consequently, snmpd reported a wrong value of the HOST-RESOURCES-MIB::hrStorageSize object when working with a large file system (larger than 16TB), because the accurate value would not fit into Integer32 as specified in the RFC. To address this issue, this update adds a new option to the /etc/snmp/snmpd.conf configuration file, realStorageUnits. By changing the value of this option to 0, users can now enable recalculating all values in hrStorageTable to ensure that the multiplication of hrStorageSize and hrStorageAllocationUnits always produces an accurate device size. On the other hand, the values of hrStorageAllocationUnits are artificial and do not represent the real size of the allocation unit on the storage device.

Comment 8 errata-xmlrpc 2012-06-20 03:21:47 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0876.html

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