Since we support the listbadblocks command, introduce the detail in the
doc.
Signed-off-by: yangerkun <yangerkun@xxxxxxxxxx>
Reviewed-by: Bryan Gurney <bgurney@xxxxxxxxxx>
---
.../admin-guide/device-mapper/dm-dust.rst | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/Documentation/admin-guide/device-mapper/dm-dust.rst b/Documentation/admin-guide/device-mapper/dm-dust.rst
index b6e7e7ead831..2c51a4acb8be 100644
--- a/Documentation/admin-guide/device-mapper/dm-dust.rst
+++ b/Documentation/admin-guide/device-mapper/dm-dust.rst
@@ -205,6 +205,23 @@ appear::
kernel: device-mapper: dust: clearbadblocks: no badblocks found
+Listing the bad block list
+--------------------------
+
+To list all bad blocks in the bad block list, run the following message
+command::
+
+ $ sudo dmsetup message dust1 0 listbadblocks
+
+The following message will appear, listing one bad block number per
+line (using an example device with blocks 1 and 2 in the bad block
+list)::
+
+ device-mapper: dust: dust_list_badblocks: badblocks list below:
+ device-mapper: dust: bad block: 1
+ device-mapper: dust: bad block: 2
+ device-mapper: dust: dust_list_badblocks: badblocks list end.
+
Message commands list
---------------------
@@ -223,6 +240,7 @@ Single argument message commands::
countbadblocks
clearbadblocks
+ listbadblocks
disable
enable
quiet
--
2.23.0.rc2.8.gff66981f45
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
