On 1 March 2012 14:10, Day, Robert <[email protected]> wrote:
> My knowledge of AllocatedUnits is the block size of the disk. I said that it
> can't handle a very large disk because of the AllocatedUnits being locked
> to block size and not a custom scale factor. Is this wrong?
> Does AllocatedUnits not HAVE to be block size?
Strictly speaking - yes it should be.
However in the case of very large disks, you've got a choice:
- you can either tell the truth about the allocation unit value,
and end up with the wrong value for overall size/usage, or
- you can lie about the allocation unit value,
and end up with the correct values for overall size/usage.
I know which one I prefer :-)
> Another note: when I said it wrapped the counter I meant it
> wrapped the Integer.... This does indeed happen on our devices.
Which version of the agent are you using?
I'd have to check the logs to be certain, but I've got a vague recollection
that the code was tweaked relatively recently (i.e in the last year or two)
to handle large disks more sensibly.
If you're using something earlier (and 5.5 came out in 2009!),
then it's definitely worth trying a more recent version.
Dave
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
