There currently seems to be no good way to handle vfs.fs.inode with BTRFS, in cases where multiple FS types expected from a LLD rule.

For example, using pused mode, will return "Cannot calculate percentage because total is zero."

This cannot currently be handled via preprocessing rule, because the item becomes unsupported before it reaches the preprocessing stage. It can also not be handled with a separate discovery rule (without the inode items), because we still cannot have duplicate item keys (vfs.fs.discovery, in this case), not even with the [] and space hacks, or dependent LLDs.

Some precedent was already created for system.swap.size: https://support.zabbix.com/browse/ZBXNEXT-6784