[PATCH V3 nvme-cli 1/2] initialize disk "access" variable

Sagi Grimberg sagi at grimberg.me
Tue Sep 28 13:45:35 PDT 2021


> (This is a prep patch, which provides functions for the next "patch 2/2")
> When it is failed to get nvme_id_ns data from NVMe Subsystem.

If there was a failure the nsid should be -1, and all the size info 
should be zero, that is enough of an indication that the ns is "faulty".

Also live/faulty is not a good terminology for path access.
Maybe full/partial or complete/incomplete.

I thought that this was about showing the completeness of the
path access for a given ns, regardless of failure of identify-ns...

Meaning that if I have a ns with 2 paths, where one is live and the
other is connecting/resetting then "Path Access" would be "incomplete"
or "partial".. Also in the case where all paths are live, but some
have ANA state "inaccessible" or "persistent loss" then "Path Access"
would be "partial" and only if all paths are "live" and ANA accessible
i.e. "optimized/non-optimized" it will show "full/complete" Path
Access...

Otherwise, I don't see the point in adding this information to
nvme list output.



More information about the Linux-nvme mailing list