From: yangerkun <yangerkun@xxxxxxxxxx>
From: yangerkun <yangerkun@xxxxxxxxxx>
Since we support the listbadblocks command, introduce the detail in the
doc.
[Bryan: formatting and wording fixes]
Signed-off-by: yangerkun <yangerkun@xxxxxxxxxx>
Signed-off-by: Bryan Gurney <bgurney@xxxxxxxxxx>
---
.../admin-guide/device-mapper/dm-dust.rst | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/admin-guide/device-mapper/dm-dust.rst b/Documentation/admin-guide/device-mapper/dm-dust.rst
index cf8079e368de..e35ec8cd2f88 100644
--- a/Documentation/admin-guide/device-mapper/dm-dust.rst
+++ b/Documentation/admin-guide/device-mapper/dm-dust.rst
@@ -206,6 +206,22 @@ appear::
dust_clear_badblocks: no badblocks found
+Listing the bad block list
+--------------------------
+
+To list all bad blocks in the bad block list (using an example device
+with blocks 1 and 2 in the bad block list), run the following message
+command::
+
+ $ sudo dmsetup message dust1 0 listbadblocks
+ 1
+ 2
+
+If there are no bad blocks in the bad block list, the command will
+execute with no output::
+
+ $ sudo dmsetup message dust1 0 listbadblocks
+
Message commands list
---------------------
@@ -224,6 +240,7 @@ Single argument message commands::
countbadblocks
clearbadblocks
+ listbadblocks
disable
enable
quiet
--
2.25.4
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
