-
New Feature Request
-
Resolution: Fixed
-
Major
-
4.0.12, 4.2.6
-
None
-
Sprint 57 (Oct 2019), Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020), Sprint 62 (Mar 2020)
-
5
We have two servers, active-pasive, sharing a file system, which is only mounted in the active node.
When server A have that FS mounted, it is reported to zabbix, via LLD, and data recolected.
ACHIEVED RESULT:
If that FS is umounted, the item "vfs.fs.size" returns the data from FS where that path exists ("/" in our case).
In Linux we see that info is recovered from statvfs, which produces that behaviour.
EXPECTED RESULT:
vfs.fs.size does not return any value if the path is not a mount point
This behaviour is observed with all Zabbix versions
Agent requests:
# zabbix_get -s hpuxnode -k "vfs.fs.size[/,pused]" 3.575193 # zabbix_get -s hpuxnode -k "vfs.fs.size[/etc,pused]" 3.575193 # zabbix_get -s hpuxnode -k "vfs.fs.size[/etc/hosts,pused]" 3.575193
Mount points:
/ on /dev/vg00/lvol3 ioerror=mwdisable,largefiles,delaylog,dev=80002003 on Fri Mar 1 10:21:10 2019
/stand on /dev/vg00/lvol1 ioerror=mwdisable,nolargefiles,log,tranflush,dev=80002001 on Fri Mar 1 10:21:17 2019
/var on /dev/vg00/lvol8 ioerror=mwdisable,largefiles,delaylog,dev=80002008 on Fri Mar 1 10:21:30 2019
/usr on /dev/vg00/lvol7 ioerror=mwdisable,largefiles,delaylog,dev=80002007 on Fri Mar 1 10:21:30 2019
/tmp on /dev/vg00/lvol6 ioerror=mwdisable,largefiles,delaylog,dev=80002006 on Fri Mar 1 10:21:30 2019
/opt on /dev/vg00/lvol5 ioerror=mwdisable,largefiles,delaylog,dev=80002005 on Fri Mar 1 10:21:30 2019
/home on /dev/vg00/lvol4 ioerror=mwdisable,largefiles,delaylog,dev=80002004 on Fri Mar 1 10:21:31 2019
