Filesystem Autodiscovery Issue

[dtedesc1]

Running Zabbix version 2.0.10 on both server and Agent. Both systems are CentOS 6.5 x86_64 with matching zabbix software using x86_64 as well.

If I run the autodiscovery from the zabbix server I get:

]# zabbix_get --host=mach --key=vfs.fs.discovery
{
        "data":[
                {
                        "{#FSNAME}":"\/",
                        "{#FSTYPE}":"rootfs"},
                {
                        "{#FSNAME}":"\/proc",
                        "{#FSTYPE}":"proc"},
                {
                        "{#FSNAME}":"\/sys",
                        "{#FSTYPE}":"sysfs"},
                {
                        "{#FSNAME}":"\/dev",
                        "{#FSTYPE}":"devtmpfs"},
                {
                        "{#FSNAME}":"\/dev\/pts",
                        "{#FSTYPE}":"devpts"},
                {
                        "{#FSNAME}":"\/dev\/shm",
                        "{#FSTYPE}":"tmpfs"},
                {
                        "{#FSNAME}":"\/",
                        "{#FSTYPE}":"ext4"},
                {
                        "{#FSNAME}":"\/proc\/bus\/usb",
                        "{#FSTYPE}":"usbfs"},
                {
                        "{#FSNAME}":"\/boot",
                        "{#FSTYPE}":"ext4"},
                {
                        "{#FSNAME}":"\/proc\/sys\/fs\/binfmt_misc",
                        "{#FSTYPE}":"binfmt_misc"},
                {
                        "{#FSNAME}":"\/misc",
                        "{#FSTYPE}":"autofs"},
                {
                        "{#FSNAME}":"\/net",
                        "{#FSTYPE}":"autofs"}]}

I see the / filesystem listed as both "rootfs" and "ext4".

I have created a template with an Autodiscovery rule:

Name: Filesystem Discovery
Type: Zabbix Agent (active)
Key: vfs.fs.discovery
Filter Macro: NONE

I have created an item prototype:

Name: Used disk space: $1
Type: Zabbix Agent (active)
Key: vfs.fs.size[{#FSNAME},used]
Type of information: Numeric (float)
Units: B

Both are enable and working with one exception. I can see all filesystems on the box in the UI with one exception the root filesystem ,"/", does not appear. I can see items for /proc, /sys, /boot, etc.

Is this by design? Is it because I should be creating a normal item to track "/" since this is a required filesystem on linux?

[dtedesc1]

Issue May Be Resolved

Doing an unlink and clear of all templates on the host, and then adding back the new template with autodiscovery seems to have fixed the issue for at least my first test server.