Debian 5.0 32bit/ Zabbix 1.4.4 and 1.8.4

no improvement in 1.9.3:

1. ./zabbix_get --version
   Zabbix Get v1.9.3 (revision 18740) (28 March 2011)
   Compilation time: Mar 29 2011 15:17:14
2. ./zabbix_get -s 10.0.0.231 -k vfs.fs.size[c:,free]
   18111352832
3. ./zabbix_get -s 10.0.0.231 -k vfs.fs.size[d:,free]
   ZBX_NOTSUPPORTED

1. ./zabbix_get -s 10.0.0.231 -k vfs.fs.size[c:,pfree]
   33
2. ./zabbix_get -s 10.0.0.231 -k vfs.fs.size[d:,pfree]
   ZBX_NOTSUPPORTED

this might actually classify as a feature request - but would need some assessment from server devs

I successfully tested with iSCSI target on OpenFiler 2.3 NAS.
Client: WinXP SP3. See a picture for a some detail.

1. zabbix_get -V
   Zabbix Get v1.9.4 (revision 18759) (28 March 2011)
   Compilation time: Mar 29 2011 15:28:42
2. zabbix_get -s 10.x.x.x -k "vfs.fs.size[h:,free]"
   34124537856
3. zabbix_get -s 10.x.x.x -k "vfs.fs.size[h:,pfree]"
   99.418716

Summary: it works !

So, maybe the different NAS impact?

Is there something else I can test to help you gain further insight in what's going wrong?

Additionally i successfully tested the big iSCSI target = 1,97 TB (2TB it's a maximum for WinXP32)

1. zabbix_get -s 10.x.x.x -k "vfs.fs.size[h:,pfree]"
   99.993840
2. zabbix_get -s 10.x.x.x -k "vfs.fs.size[h:,free]"
   2173519679488

Gertjan, what windows version you use?
Microsoft iSCSI Software Initiator Version 2.08 used?

Windows server 2008 Small Business Server. About the ISCSI software initiator version: really no idea how to check that: I looked at every window in control panel -> iscsi initiator and Server Managemer -> Disk manager, but can't find out which version the server uses. When I look at the release notes from Microsoft for version 2.08, it says that in that version, file msiscsi.sys should be version 5.2.3790.3825, mine says version 6.0.6002.18005
(by the way: 42TB is quite nice for al your pr0^H^H^H important files

Gertjan, i recall Microsoft iSCSI Software Initiator included into 2008 server out of the box.
Which architecture of your 2008 server - x32 or x64 ? I know that 2008 R2 is only x64, but maybe SBS can be 32x too.
I hope you tried to restart (reboot) all stuff, just for case

Hi Oleksiy, it's 64bit, machine is up since january 21st. Since it is indeed an operating system that needs rebooting for the most trivial operating system tasks and for reasons only known (at least, I hope) to MS developers, I will ask the customer to reboot the server, I'll let you know.
In the meantime, if I can get you more relevant data, please let me know.

Gertjan, try to reproduce the problem with the small target, for example 3 GB. And report here.

Gertjan, special for you I've installed 2008 server R2 x64 (not SBS) for testing.
Used zabbix_agent x64 version. Attached two iSCSI targets (with a maximum size as i can). See picture "two_iscsi.png"

Resuls:

1. zabbix_get -s 10.x.x.108 -k "vfs.fs.size[E:,free]"
   7967428972544
2. zabbix_get -s 10.x.x.108 -k "vfs.fs.size[F:,free]"
   6000763068416
3. zabbix_get -s 10.x.x.108 -k "agent.version"
   1.9.3
4. zabbix_get -s 10.x.x.108 -k "system.uname"
   Windows WIN-SR8VR75TFE9 6.1.7600 Windows Server 2008 AMD-64

All works ! So, i will not test anything anymore. Good luck

Cool, thanks for testing, that tells me that probably not a lot of people will have the issues I have. So the only difference is the windows version of our customer:
Windows TS001 6.1.7600 Windows NT 6.1 AMD-64
and the type of NAS used (Synology DS411+)

I'll try to reproduce the problem myself, getting a synology somewhere, I'll keep you posted: either I can reproduce the problem or it is a single incident.

OMG I think I'm gonna cry....server finally got rebooted and guess what: it's working again. I am so sorry for wasting your time like this: In case you come to Holland please let me know, I'll buy you a beer.
Another fine example of the fact that rebooting windows actually solves "unexpected behaviour".
I will close the call, and next time, reboot prior to doing anything else about it

windows == reboot. Always. Every time.

That is good. But need to reopen and close as Cannot reproduce.