Some days ago I had problems with Custom multiplier and Network Traffic but I doesn't waste time to test and I removed the Custom multiplier. Today I observed that some of my servers have PB (PetaByte-Disks) or Disks with some hundreds of TB - but I'm sure they don't have

Exactly the trigger on
vfs.fs.size[/,total]
uses in my template a Custom multiplier of 1024 and Units "B". Some dozens of Linux-Servers with Agent-versions 1.4.6 or 1.6.1 show the right size but every Server with an 1.8.2-Agent shows 1024 (or 1000?) times to much total disk space. I don't know if the problem is the multiplier itself or the response from the client.
An example:
That are with Custom Multiplier 1.35 PB but the right size of this disc is 1.4 TB. Can anyone put this on bugtracker please? 
Edit: server is Zabbix 1.8.2 on Debian Squeeze

Exactly the trigger on
vfs.fs.size[/,total]
uses in my template a Custom multiplier of 1024 and Units "B". Some dozens of Linux-Servers with Agent-versions 1.4.6 or 1.6.1 show the right size but every Server with an 1.8.2-Agent shows 1024 (or 1000?) times to much total disk space. I don't know if the problem is the multiplier itself or the response from the client.
An example:
zabbix_get -s1.2.3.4 -p10050 -k"vfs.fs.size[/,total]"
1486071214080
1486071214080

Edit: server is Zabbix 1.8.2 on Debian Squeeze
That's a little bit ugly if you have many different systems. I have most servers on Debian stable but some are with testing/unstable-Packages or with Ubuntu and on a Debian-system I hate it to use packages which are not in the official mirrors. The Winmachines are not a problem for me, they are all with v1.8.2.
Comment