nvme/nvme-cli
1
0
Fork 0
Code Issues Activity

Adding upstream version 2.7.1.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-16 12:25:41 +01:00
parent 04338f02fe
commit d6e1a5d456
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
663 changed files with 15529 additions and 6994 deletions
Download patch file Download diff file Expand all files Collapse all files

7
Documentation/nvme-toshiba-vs-smart-add-log.html
View file

@ -764,7 +764,8 @@ request and either saves the result to a file or dumps the content to stdout.</p
<div class="paragraph"><p>The &lt;device&gt; parameter is mandatory and may be either the NVMe
character device (ex: /dev/nvme0), or a namespace block device (ex:
/dev/nvme0n1).</p></div>
<div class="paragraph"><p>The log contents may be associated with the controller, in which case the namespace parameter is ignored.</p></div>
<div class="paragraph"><p>The log contents may be associated with the controller, in which case the
namespace parameter is ignored.</p></div>
<div class="paragraph"><p>Two logs exist, page 0xC0 (log page directory) and page 0xCA (vendor log page)</p></div>
<div class="paragraph"><p>This will only work on Toshiba devices supporting this feature.</p></div>
</div>
@ -781,7 +782,7 @@ character device (ex: /dev/nvme0), or a namespace block device (ex:
</dt>
<dd>
<p>
Log page: 0xC0 or 0xCA (defaults to 0xCA)
Log page: 0xC0 or 0xCA (defaults to 0xCA)
</p>
</dd>
<dt class="hdlist1">
@ -840,7 +841,7 @@ Get the contents of log page 0xC0 from the device and save to a binary file:
<div id="footer">
<div id="footer-text">
Last updated
2023-09-29 08:33:07 CEST
2023-12-21 15:49:29 CET
</div>
</div>
</body>