the previous commit 2eab6784c052335efa1a58c97ce2827970dbf2fc introduced an issue because it used a capturing group for 0x. All groups after this were off by one then and the usage always reported as 0.
Unfortunately i only noticed this today because a few servers i have a warning when nvme reported usage is 0.
the previous commit 2eab6784c052335efa1a58c97ce2827970dbf2fc introduced an issue because it used a capturing group for 0x. All groups after this were off by one then and the usage always reported as 0.
Unfortunately i only noticed this today because a few servers i have a warning when nvme reported usage is 0.
Info @wt-io-it