You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
by my interpretation of the README and --help, specifying one or more --smartctl.device= arguments should disable the device scanning in favor of a static list.
On some of my systems this seems to not be the case, launching the exporter with
whereas I expected to only have /dev/sda and /dev/sdb show up.
Similarly, the exported metrics contain all the other devices.
It does work as expected on other systems (ones with < 10 disks) with the same command line and exporter version (0.12.0), the issue only exists on the ones with large amounts of disks.
Smartd/smartctl natively handle it correctly and exclusively handle the two devices with them listed in /etc/smartd.conf.
Any ideas what's different on the problematic systems (other than the large amount of disk devices)?
Most of the additional disks are from SAN storage, but I would assume the smartctl.device option to work equally for anything /dev/sdX?
The text was updated successfully, but these errors were encountered:
This is my bad - I accidentally built from master. The issue is with the patch from #205 which disables the smartctl.devices logic (interestingly keeping the argument, albeit it not doing anything) but is not present in the tagged release.
Hi,
by my interpretation of the README and
--help
, specifying one or more--smartctl.device=
arguments should disable the device scanning in favor of a static list.On some of my systems this seems to not be the case, launching the exporter with
on them yields
Heavily truncated output
whereas I expected to only have
/dev/sda
and/dev/sdb
show up.Similarly, the exported metrics contain all the other devices.
It does work as expected on other systems (ones with < 10 disks) with the same command line and exporter version (0.12.0), the issue only exists on the ones with large amounts of disks.
Smartd/smartctl natively handle it correctly and exclusively handle the two devices with them listed in
/etc/smartd.conf
.Any ideas what's different on the problematic systems (other than the large amount of disk devices)?
Most of the additional disks are from SAN storage, but I would assume the
smartctl.device
option to work equally for anything/dev/sdX
?The text was updated successfully, but these errors were encountered: