[Nagiosplug-devel] check_disk plugin fails on 80 TB filesystem

Thomas Guyot-Sionnest thomas at zango.com
Fri Sep 21 23:13:02 CEST 2007

Hash: SHA1

Matthias Eble wrote:
>> I'm not sure if this is an issue of having to use statfs64 vs statfs, or
>> an issue of variable sizes too small.  I'll be glad to test any patches...
> Is this a linux system?
> If yes, can df display these sizes without problems?

Ideally we'd need to know:

- - The type/version of operating system (uname -a)
- - The type of executables (32, 64bit?). (file /path/to/check_disk)
- - Which compiler (cc -v, cc --version, cc -V, ???)
- - The full output of strace or equivalent, if possible.

Also did you compile Nagios-plugins on that server or on another?

- -----

I did some testing with a 80TiB loop device on my computer (Ubuntu
64Bit) and check_disk works like a charm on it. I then copied a 32bit
check_disk binary from a server and ran it: it failed.

- From strace I can see that the same statfs call that works with the
64bit library returns -1 EOVERFLOW (Value too large for defined data
type) on the 32bit libs, though I have no idea if it's the same kind of

I also tested artificially setting the variables that are normally set
by get_fs_usage(). It worked nicely on 64-bit systems (Ubuntu 64,
Solaris 10), while on 32bit the perfdata part was broken (the functions
uses signed integers). In both case the alerting worked properly though.

- --
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Devel mailing list