windows os with floppy drive

There is no way to increase timeout for discovery items only. Note that all items (discovery or not) process timeout in exactly the same manner. You may increase Timout parameter in zabbix_agentd.conf and zabbix_server.conf, but it is absolutely not recommended solution.

I am closing it because it is not a bug report.

The problem is:
If you activate "Mounted filesystem discovery"(from default template) for the hosts with floppy disk drive and Windows installed, then we start to get messages like "Zabbix agent on HOST is unreachable for 5 minutes"

This problem because of the function GetVolumeInformation (diskspace.c file) trying to get info about floppy disk drive filesystem. It gets about 5-6 second, so we get timeout.
Think that it's a good idea to exclude disk "a:" from filesystem check in agentd.

The problem is:
If you activate "Mounted filesystem discovery"(from default template) for the hosts with floppy disk drive and Windows installed, then we start to get messages like "Zabbix agent on HOST is unreachable for 5 minutes"

This problem because of the function GetVolumeInformation (diskspace.c file) trying to get info about floppy disk drive filesystem. It gets about 5-6 second, so we get timeout.
Think that it's a good idea to exclude disk "a:" from filesystem check in agentd.

This is not a bug, bun if you want to add file system discovery to a number of windows servers with floppy drives, you will get a lot of "Zabbix agent on HOST is unreachable for 5 minutes" problems. And this is not good.

i'm not quite sure whether it's a good idea to hardcode such exceptions, especially given the demise of floppy drives. nevertheless, moving to feature requests first

Just a link - a forum thread (in Russian) http://www.zabbix.com/forum/showthread.php?p=120902
http://www.zabbix.com/forum/showthread.php?p=124056

I don't think this should be triaged as a minor feature request.

vfs.fs.discovery is not a simple item, but a metaitem where actual items are derived from. The file system discovery always timing out if certain devices are installed invalidates the purpose of autodiscovery because no storage item will be created, this makes file system autodiscovery unreliable.

It's telling that you have to disable storage devices to make storage autodiscovery work.

I've found file system discovery works if the item type of the discovery rule is changed from "zabbix agent" to "zabbix agent (active)", even if the manual for 2.2 states

The type of check to perform discovery; should be Zabbix agent for file system discovery.

This makes sense as the server timeout is only for passive checks, active checks can take all the time they need. I guess all hosts that can be passive checked are capable of active checks, so this issue is not that serious after all.

note that manual has been updated to mention both 'normal' (passive) agent & active agent as valid choices for this discovery rule

additionally, ZBX-4284 talks about having an algorithm to disable only the items that are timing out. while it won't solve the main problem here, it would prevent host from being reported as being down

features used in ZBXNEXT-2006 might be considered to improve current case, if it still will be actual.