hrStorageSize limits
Bobby Krupczak <rdk@empiretech.com> Tue, 24 September 1996 05:09 UTC
Received: from cnri by ietf.org id aa20421; 24 Sep 96 1:09 EDT
Received: from ANDREW.CMU.EDU by CNRI.Reston.VA.US id aa10689; 24 Sep 96 1:09 EDT
Received: (from postman@localhost) by andrew.cmu.edu (8.7.5/8.7.3) id XAA07589; Mon, 23 Sep 1996 23:33:51 -0400
Received: via switchmail for hostmib+@andrew.cmu.edu; Mon, 23 Sep 1996 23:33:48 -0400 (EDT)
Received: from po2.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q000/QF.kmFpF2200Uda82j04M>; Mon, 23 Sep 1996 23:23:48 -0400 (EDT)
Received: from emptech.empiretech.com (emptech.empiretech.com [198.17.251.1]) by po2.andrew.cmu.edu (8.7.5/8.7.3) with ESMTP id XAA00676 for <hostmib@andrew.cmu.edu>; Mon, 23 Sep 1996 23:23:30 -0400
Received: from ottoman.empiretech.com (ottoman.empiretech.com [198.17.251.2]) by emptech.empiretech.com (8.6.12/8.6.12) with ESMTP id XAA06093 for <hostmib@andrew.cmu.edu>; Mon, 23 Sep 1996 23:23:25 -0400
Received: (from rdk@localhost) by ottoman.empiretech.com (8.7.5/8.6.12) id XAA01363 for hostmib@andrew.cmu.edu; Mon, 23 Sep 1996 23:23:24 -0400 (EDT)
From: Bobby Krupczak <rdk@empiretech.com>
Message-Id: <199609240323.XAA01363@ottoman.empiretech.com>
Subject: hrStorageSize limits
To: hostmib@andrew.cmu.edu
Date: Mon, 23 Sep 1996 23:23:23 -0400
X-Mailer: ELM [version 2.4 PL22]
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Hi! >RFC1514 defines the hrStorageSize as SYNTAX INTEGER (0..2147483647). >The size of file systems may go beyond this range. The statvfs struct >on SVR4 machines defines the number of blocks on a certain file system >as an u_long variable. This is larger than the above value. Upcoming >64 bit machines will need even larger values of hrStorageSize than >4294967295! One way to work around this problem may be to use an >artificial value for hrStorageAllocationUnits. But then >hrStorageAllocationUnits is no longer the size of allocated data >objects as defined in the MIB definition. Dont forget that this limitation effects other storage areas as well. When testing our HostMIB agent on a Sun Enterprise 6000, we ran into this problem with non-disk related storage areas as well. Our implementation does the above for things like memory. Although you can allocate memory down to the byte-level, our private-enterprise MIB measures it in units of Kbytes and we therefore get around the above limits. Bobby rdk@empiretech.com
- hrStorageSize limits Ulrich Haebel SNI
- hrStorageSize limits Bobby Krupczak