limit on vfs.fs.size?

[garumph]

I have a system with several large mount points. It looks like zabbix is not supporting vfs.fs.size on file systems larger than 2T. Is this the case and is there a workaround? This is kind important in our environment:

df -h:

store01/backup/depot 23T 241G 19T 2% /store01/backup/depot
store01/backup/prod 23T 3.7T 19T 17% /store01/backup/prod
store01/backup/uunas01
1.0T 77G 947G 8% /store01/backup/uunas01
store01/dws/dws_admin
75G 3.3G 71G 5% /store01/dws/dws_admin

[root@mon02 ~]# zabbix_get -s store01.prod.sea2.cmates.com -k vfs.fs.size[/store01/backup/depot,pfree]
ZBX_NOTSUPPORTED
[root@mon02 ~]# zabbix_get -s store01.prod.sea2.cmates.com -k vfs.fs.size[/store01/backup/prod,pfree]
ZBX_NOTSUPPORTED
[root@mon02 ~]# zabbix_get -s store01.prod.sea2.cmates.com -k vfs.fs.size[/store01/backup/uunas01,pfree]
92.433821
[root@mon02 ~]# zabbix_get -s store01.prod.sea2.cmates.com -k vfs.fs.size[/store01/dws/dws_admin,pfree]
95.622716

[slash5k1]

vfs.fs.size [m|ZBX_NOTSUPPORTED]

Hi, i too have hit this problem...

running truss on the agent gives the lovely error of:
statvfs("/tank1", 0x08044B40) Err#79 EOVERFLOW
(full dump attached)

uname -a
SunOS san1 5.11 snv_111b i86pc i386 i86pc Solaris
(open solaris 2009.6)

isainfo -kv
64-bit amd64 kernel modules

i suspect this could be a 32bit issue / 2TB limit

possible patch guys ??

Cheers,


Chris

[slash5k1]

further to this...

looking at man statvfs

ERRORS
The statvfs() and fstatvfs() functions will fail if:

EOVERFLOW One of the values to be returned cannot be
represented correctly in the structure pointed
to by buf.

then down the bottom of the page we have this...

USAGE
The statvfs() and fstatvfs() functions have transitional
interfaces for 64-bit file offsets. See lf64(5).


looking at man lf64 i can also see this...

<sys/statvfs.h>
int statvfs(..., int statvfs64(...,
struct statvfs *); struct statvfs64 *);
int fstatvfs(..., int fstatvfs64(...,
struct statvfs *); struct statvfs64 *);

i suspect here this could be the problem?

[slash5k1]

solved (for opensolaris 2009.6 64bit)

this is what i did to resolve my issue:

tar -vzxf zabbix-1.6.6.tar.gz
cd zabbix-1.6.6
for file in `find * | xargs grep -i -l statvfs` ; do perl -pi -e 's#statvfs#statvfs64#g' $file ; done
./configure --enable-agent
make
./src/zabbix_agent/zabbix_agentd -t vfs.fs.size[/tank1,free]

i now get the output:
vfs.fs.size[/tank1,free] [u|4056248459]

I have no idea if this impacts any of the other supported OS's ?

Please can you add this 64bit support to solaris

thankyou!

Chris

[sgbeal]

workaround for vfs.fs.free limit on 2TB+

Here's the workaround i use locally for the systems which have >2TB:

# hvb.fs.freekb[/path] returns free space in kb. The perl weirdness here is to avoid
# extra $'s (behaviour/escaping of which are not documented in the Zabbix docs) in an
# AWK expression. In Zabbix Item Configuration:
# Type=Numeric (int64), Units=B, Custom Multiplier=1024
# will result in gigabytes.
UserParameter=hvb.fs.freekb[*],df -b $1 | sed 1d | perl -pe 's/\s+/:/g;' | cut -d: -f2

("hvb" is the organization's name - feel free to change it to suit)

This can certainly be done more easily, but i've only been working with Zabbix for about 4 hours.

PS: tested on Solaris 10 64bit Sparc.