ExportXMLWordPrintable

    • Type: Problem report
    • Resolution: Unresolved
    • Priority: Trivial
    • 7.0.31
    • Affects Version/s: 7.0.32
    • Component/s: Agent2 plugin (G)
    • None
    • Environment:

      Steps to reproduce:

      1. On a host with this configuration, run zabbix_agent2 -t 'smart.disk.discovery[id]'. Compare the discovery entry for the same physical disk before and after upgrading the agent from 7.0.31 to 7.0.32.
      1. On 7.0.32, query that disk explicitly through each path. The following commands refer to the same disk on the affected host:
        {{zabbix_agent2 -t 'smart.disk.get[/dev/disk/by-id/ata-ST20000NM007D-3DJ103_ZVTD8JE8,"sat"]'
        zabbix_agent2 -t 'smart.disk.get[/dev/bus/0,"megaraid,81"]'}}

      Result:

      Before the upgrade, Zabbix collected data through the disk/by-id/… sat item with exit status 0. After the upgrade, discovery selected bus/0 megaraid,81. Both paths still work on 7.0.32, but they return different results:

      Access path Serial number exit_status Agent error field
      /dev/disk/by-id/ata-…, sat ZVTD8JE8 0 Empty
      /dev/bus/0, megaraid,81 ZVTD8JE8 4 Warning: This result is based on an Attribute check.

      Tracing smartctl -H on the MegaRAID path identifies the specific failure: ATA return descriptor not supported by controller firmware. The direct SAT path successfully returns the SMART health status. Both paths report the same temperature and 22 ATA SMART attributes.

      The change also alters {{{}

      {#NAME}

      {}}}, so Zabbix creates new items for a disk that already has history under its stable by-id name. Following the upgrade, we observed 607 Some command to the disk failed events across 13 storage hosts. For 606 of those entries, Zabbix had a prior direct-path item on the same host with the same serial number. The side-by-side command results above were verified on one affected host.

      Expected:

      When smart.disk.discovery[id] finds the same serial number through a working /dev/disk/by-id/ SAT path and a MegaRAID path, it should retain the stable by-id path. A disk accessible only through MegaRAID should still be discovered, including when smartctl returns useful data with a nonzero exit status.

      Possible cause

      The fix for ZBX-26359 allows the MegaRAID result with exit status 4 to participate in discovery. When both paths are present, parseOutput() sorts their names and keeps the first entry for each serial number. /dev/bus/0 sorts before /dev/disk/by-id/…, so the path with limited SMART command support wins. This appears to be a side effect of path selection during deduplication. ZBX-26359 (https://support.zabbix.com/browse/ZBX-26359) · Deduplication code in 7.0.32 (https://github.com/zabbix/zabbix/blob/7.0.32/src/go/plugins/smart/smartfs.go#L611-L627)

            Assignee:
            Zabbix Support Team
            Reporter:
            Ivan Prokudin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: