Make the stat tag a disk level

This commit is contained in:
Andrea Mazzoleni 2025-12-26 11:12:22 +01:00
parent 672b881df3
commit 524733a6db
6 changed files with 67 additions and 140 deletions

View file

@ -1444,8 +1444,11 @@ attributes, but with the risk of spinning up all disks.
.PP
Note that a \`<disk_name>\` may be associated with more \`<device_file>\`,
in case the logical disk uses more physical disks. In such a case,
you\'ll see multiple tags for the same \`<disk_name>\` but with different
\`<device_file>\`.
you\'ll see multiple \`<attr>\` and \`<smart>\` tags for the same
\`<disk_name>\` but with different \`<device_file>\`. The exception is the
\`stat\` attrbute that is cumulative for all the devices part of the
disk.
.PP
In case of split parity, the parity name is followed by \`/N\` to indicate
the split index, where N starts from 0. The \`/0\` is always omitted.
.SS Attributes
@ -1597,8 +1600,10 @@ read.
Logs a successful spin\-down operation initiated via the
smartctl command.
.TP
.B attr:<device_file>:<disk_name>[/<split_index>]:stat:<access_number>
Logs the total number of read and write accesses done on the disk.
.B stat:<disk_name>:<access_number>
Logs the total number of read and write accesses done on the
disk. This is a cumulative value that include all the devices
and split of the disk.
Comparing this number at different times, you can detect if the
disk was used during that time.
.RS 4

View file

@ -926,8 +926,11 @@ Command Smart And Probe Tags
Note that a `<disk_name>` may be associated with more `<device_file>`,
in case the logical disk uses more physical disks. In such a case,
you'll see multiple tags for the same `<disk_name>` but with different
`<device_file>`.
you'll see multiple `<attr>` and `<smart>` tags for the same
`<disk_name>` but with different `<device_file>`. The exception is the
`stat` attrbute that is cumulative for all the devices part of the
disk.
In case of split parity, the parity name is followed by `/N` to indicate
the split index, where N starts from 0. The `/0` is always omitted.
@ -1020,8 +1023,10 @@ Command Smart And Probe Tags
Logs a successful spin-down operation initiated via the
smartctl command.
=attr:<device_file>:<disk_name>[/<split_index>]:stat:<access_number>
Logs the total number of read and write accesses done on the disk.
=stat:<disk_name>:<access_number>
Logs the total number of read and write accesses done on the
disk. This is a cumulative value that include all the devices
and split of the disk.
Comparing this number at different times, you can detect if the
disk was used during that time.

View file

@ -968,8 +968,11 @@ attributes, but with the risk of spinning up all disks.
Note that a `<disk_name>` may be associated with more `<device_file>`,
in case the logical disk uses more physical disks. In such a case,
you'll see multiple tags for the same `<disk_name>` but with different
`<device_file>`.
you'll see multiple `<attr>` and `<smart>` tags for the same
`<disk_name>` but with different `<device_file>`. The exception is the
`stat` attrbute that is cumulative for all the devices part of the
disk.
In case of split parity, the parity name is followed by `/N` to indicate
the split index, where N starts from 0. The `/0` is always omitted.
@ -1062,8 +1065,10 @@ Tags logging specific disk identification and attribute values.
Logs a successful spin-down operation initiated via the
smartctl command.
attr:<device_file>:<disk_name>[/<split_index>]:stat:<access_number>
Logs the total number of read and write accesses done on the disk.
stat:<disk_name>:<access_number>
Logs the total number of read and write accesses done on the
disk. This is a cumulative value that include all the devices
and split of the disk.
Comparing this number at different times, you can detect if the
disk was used during that time.