good day.
long time zabbix user - just noticed that on some newer macOS devices (13+) that the vfs.fs.size key reports the wrong values. It is seemingly maxed out to some degree at a much lower value than the 64-bit unsigned integer should hold. has anyone noticed this? I could build some custom keys to get the proper values via some other means but i am wondering why this is happening.
some examples:
but zabbix_get gets:
~ 408 GB
on another machine i have:
but they report:
thank you!
oh also pfree does not work...
long time zabbix user - just noticed that on some newer macOS devices (13+) that the vfs.fs.size key reports the wrong values. It is seemingly maxed out to some degree at a much lower value than the 64-bit unsigned integer should hold. has anyone noticed this? I could build some custom keys to get the proper values via some other means but i am wondering why this is happening.
some examples:
Code:
/dev/disk5s1 16Ti 1.1Ti 15Ti 7% 713 164070039840 0% /Volumes/G-DRIVE
but zabbix_get gets:
Code:
zabbix_get -s 127.0.0.1 -p 10050 -k 'vfs.fs.size["/Volumes/G-DRIVE",total]' 407812136960
~ 408 GB
on another machine i have:
Code:
/dev/disk9s1 16Ti 57Gi 16Ti 1% 1.9k 175G 0% /Volumes/18 TB OWC Gemini RAID /dev/disk7s1 16Ti 3.7Ti 13Ti 23% 1.0M 136G 0% /Volumes/18 TB WD RAID
Code:
zabbix_get -s 127.0.0.1 -p 10050 -k 'vfs.fs.size["Volumes/18 TB OWC Gemini RAID",total]' 407778582528
Code:
zabbix_get -s 127.0.0.1 -p 10050 -k 'vfs.fs.size["Volumes/18 TB WD RAID",total]' 407677894656
oh also pfree does not work...
Code:
zabbix_get -s 127.0.0.1 -p 10050 -k 'vfs.fs.size["Volumes/18 TB WD RAID",pfree]' 0.000000