-
Notifications
You must be signed in to change notification settings - Fork 665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nvme: fix verbose logging for certain commands #2406
Conversation
The verbose option shows detail information if twice input as |
Yes, I know. But the current
As described above, this patch only fixes the |
I like the idea to use |
Ah, ok. So basically you are asking to:
Will give that a try here. |
Yes. I agree with your reasoning to retire IIRC, the latency output is printed at INFO level instead of DEBUG. |
9c4b119
to
64349b2
Compare
The -v verbose option for certain nvme commands like id-ctrl, id-ns, smart-log, sanitize-log, etc. is practically a no-op since it only prints latency info in addition to the regular output. But at the same time, these commands already implement a -H human readable option which prints additional useful info. So fix the -v option to make it synonymous with the -H option here. And while we are at it, move the latency info from current INFO level (i.e. -v logging) to DEBUG level (i.e. -vv logging) since it is better suited there. Signed-off-by: Martin George <[email protected]>
64349b2
to
86b9464
Compare
Thanks! |
Verbose logging for certain nvme commands like id-ctrl, id-ns, smart-log, sanitize-log, etc. does not print anything additional or verbose compared to the regular output. These commands already implement a human-readable option which works fine, but it is the verbose option that is broken. So fix the verbose option here to ensure it is on par with the human-readable option. Later if required, we can eliminate any one of these options for these commands to avoid redundancy.