problem with measuring teroctet disk space

[Patrick_C]

Hello,

I am having troubles with zabbix v1.4.4 measuring total disk space and free disk space on a Windows Server 2003.
It seems that zabbix is not able to measure disk space higher than a teraoctet.

Is there anybody having knowledge on this kind of problem?

Patrick

[hyarion]

It looks like it might be the database side. If I look at my mysql database table 'history' for zabbix it shows that the history field is DOUBLE(16,4) - this means 16 digits (up to 4 go after the decimal point) for octets.

This means a max of 9,999,999,999,999,999. Just short of 10 petaoctet if I'm correct. I don't know too much about numeric types though, so it could be lower requiring at least 1 decimal point - i.e. 999,999,999,999,999.9 - just short of 1 petaoctet.

In order to record a value higher than that the database would need to be adjusted, however there might be other circumstances which would still restrict it - e.g binary might not support larger numbers, php might need adjusting, other tables might need to be adjusted.

[Patrick_C]

Thank you for your help.
To change this type I have to modify the source code and to recompile zabbix, right? Or can it be done by configuring zabbix?

[Patrick_C]

I've decided to migrate to 1.6.5 version after having found the ZBX-93 bug report.
But the database upgrade doesn't change the column size of value field in history table. It still is (16,4).
Since I haven't large HD (>1Tbyte to reproduce the problem) I cannot check the resolution of the problem.

Does anyone measure >1TByte disk space with Zabbix 1.6.5? or with other versions?

regards

PS: teraoctet=terabyte :)

[EnigmA-X]

You can try to receive the value from the command-line with zabbix_get -s <target> -k <key> and see what it returns.

This way you can check if it fits into the database.