[ZBX-24762] vfs.fs.get timeout when some network mount points are unreachable Created: 2024 Jul 02  Updated: 2025 May 12

Status: Open
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: None
Fix Version/s: None

Type: Patch request Priority: Trivial
Reporter: Michaël PAULON Assignee: Vjaceslavs Smelovs
Resolution: Unresolved Votes: 6
Labels: vfs.fs.get
Remaining Estimate: Not Specified
Time Spent: 7h
Original Estimate: Not Specified


 Description   

Steps to reproduce:

  1.  run `zabbix_agentd -t vfs.fs.get` on a system with unreachable network mount points (in our case managed by autofs) still in `/proc/mount`

Result:
`[m|ZBX_NOTSUPPORTED] [Timeout while waiting for data.]`
Expected:
The request should succed but some mount points should be flagged as unreachable/failed/down.

Looking at the source code `vfs.fs.get` does the following:
 - read `/proc/mount`
 - for each line get stats with `statfs/statvfs`. 
When a network mount point is still in `/proc/mount` but is no longer reachable the `statfs/statvfs` request will hang until the network service responsible for mounting (here autofs) times out.
This might lead to cases where the whole `vfs.fs.get` request times out and no data is returned even if all the other mount points are available.

A solution could be to add another "layer" of timeout for each `statfs/statvfs` request to prevent the whole request to fail.



 Comments   
Comment by Mariusz Lewandowski [ 2024 Dec 12 ]

Issue is still observable on Zabbix agent 7.0.4. Huge problem for a lot of systems, when the connection to NFS mounts is unstable. 

Generated at Tue May 13 09:17:18 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.