On Sat, 25 Nov 2017 11:42:07 -0700 Joel Knight <knight.j...@gmail.com> wrote: > On Thu, Mar 9, 2017 at 10:02 PM, Joel Knight <knight.j...@gmail.com> wrote: > > Hi. > > > > snmpd(8) uses unsigned ints internally to represent the size and used > > space of a file system. The HOST-RESOURCES-MIB defines the valid > > values for those OIDs as 0..2147483647. With sufficiently large file > > systems, this can cause negative numbers to be returned for the size > > and used space OIDs. > > > > .1.3.6.1.2.1.25.2.3.1.5.36=-1573167768 > > Hi. Just wanted to bump this again and see if anyone that cares about > snmp could take a look? Looking for oks and someone who wouldn't mind > committing it. > > > > At sthen's suggestion, do what net-snmp does and fiddle with the > > values to prevent wrapping. Yes this mucks with the actual values of > > size, used space, and block size, but it allows snmpd to convey the > > proper size and used space of the file system which is what most > > everybody is really interested in. > > > > In case gmail hoses this diff, it's also here: > > https://www.packetmischief.ca/files/patches/snmpd.hrstorage2.diff
Hi Joel, I think this won't work unless you also change the type of 'size' and 'used' to u_int64_t. Gerhard
