On 07/07/2013 8:00 AM, "Tom Laermans" <tom.laermans@powersource.cx> wrote:

Space looks OK to me, but I don't have large volumes (1.5TB is the largest) on my Windows machines.

How are your other tools monitoring this? Can you perhaps post a debug poller log? (strip out the community) - I wonder if Windows is reporting it wrong or if we're doing it wrong.

Tom

On 4/07/2013 23:40, DaZZa wrote:

On 4 July 2013 17:28, Tom Laermans <tom.laermans@powersource.cx> wrote:

Hi,

You can change to v2c in the device settings, no need to delete and re-add.

Yeah, I found that, but I wasn't 100% sure it would eliminate the
problem, so I went down the "delete and recreate" path. It's not like
there was historical data I needed anyway. :-)

This may be a Windows problem, do you or anyone else have other machines
with >16TB of diskspace on Windows?

I don't - while my VMWare cluster has that much raw storage, it's
broken into smaller chunks for compatibility reasons. This server is
stand-alone.

For example, until Net-SNMP 5.7 there was no way to correctly
monitor/graph/detect disk sizes over 16TB on Linux either. 5.7 added support
for larger counters, which we now use.

There may be a similar limitation on Windows. (but I guess it is possible
that this requires v2c and you're not using it)

Well, I'm now running the server with v2c, and it still doesn't read
the volume size correctly.

It's not a major issue - I'll just set Observium to ignore the volume,
since I have other monitors on it (users who will scream "IT!!!!" in a
loud voice if it runs out of space), and the important volumes (the OS
and system disks) are picked up OK.

Thanks.

DaZZa
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium