diff options
| author | Nilay Shroff <nilay@linux.ibm.com> | 2026-05-17 00:06:50 +0530 |
|---|---|---|
| committer | Keith Busch <kbusch@kernel.org> | 2026-06-04 01:57:19 -0700 |
| commit | 66ee95b3d490d78283b6e92cb4230d4a04c99817 (patch) | |
| tree | 0e7808b518383a153a56e10720a947ebf3c59caf /include/linux/timerqueue_types.h | |
| parent | ab5af2903baa472930c94a421efdd22a49036213 (diff) | |
nvme: export multipath failover count via sysfs
When an NVMe command completes with a path-specific error, the NVMe
driver may retry the command on an alternate controller or path if one
is available. These failover events indicate that I/O was redirected
away from the original path.
Currently, the number of times requests are failed over to another
available path is not visible to userspace. Exposing this information
can be useful for diagnosing path health and stability.
Export per-path sysfs attribute "multipath_failover_count" under diag
attribute group. This attribute is both readable and writable and thus
allowing user to reset the counter. This counter can be consumed by
monitoring tools such as nvme-top to help identify paths that
consistently trigger failovers under load.
Tested-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'include/linux/timerqueue_types.h')
0 files changed, 0 insertions, 0 deletions
