This is very similar to ZBX-18944 which was apparently fixed but the issue persists in 6.4.x and possibly 6.0.x given the comments.{}

Steps to reproduce:

1. Add PVC volume to kubernetes host, or any long fs name
2. Add host via zabbix agent2 to zabbix, and add default Linux template
3. Open Configuration > Hosts > select host
4. Select Discovery Rules in top menu
5. Click red  symbol next to „Template Module Linux filesystems by Zabbix agent: Mounted filesystem discovery"

Result:

PVCs are not discovered, as trigger creation fails.

Cannot create trigger: value "/hostfs/root/var/lib/kubelet/pods/0fb86686-d0ec-40cf-81bc-7306dd4fd9af/volumes/kubernetes.io~csi/pvc-8303b2ce-a97c-4a7a-9d5b-923f3395870a/mount: Running out of free inodes (free < {$VFS.FS.INODE.PFREE.MIN.CRIT:"/hostfs/root/var/lib/kubelet/pods/0fb86686-d0ec-40cf-81bc-7306dd4fd9af/volumes/kubernetes.io~csi/pvc-8303b2ce-a97c-4a7a-9d5b-923f3395870a/mount"}%)" is too long.

Expected:
Trigger creation succeeds.