Since we can list bad blocks with command status, introduce the detail
in the doc.
Signed-off-by: yangerkun <yangerkun@xxxxxxxxxx>
---
.../admin-guide/device-mapper/dm-dust.rst | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/Documentation/admin-guide/device-mapper/dm-dust.rst b/Documentation/admin-guide/device-mapper/dm-dust.rst
index b6e7e7ead831..9267d9330482 100644
--- a/Documentation/admin-guide/device-mapper/dm-dust.rst
+++ b/Documentation/admin-guide/device-mapper/dm-dust.rst
@@ -205,6 +205,20 @@ appear::
kernel: device-mapper: dust: clearbadblocks: no badblocks found
+Listing the bad blocks
+----------------------
+
+After we have add some bad blocks(like block 1 and 2), run the following
+command can help us to check the bad blocks::
+
+ $ sudo dmsetup status dust1
+ 0 33552384 dust 252:17 bypass verbose badblocks list: 1 2
+
+And if there is no bad blocks, we will get following results::
+
+ $ sudo dmsetup status dust1
+ 0 33552384 dust 252:17 bypass verbose badblocks list: null
+
Message commands list
---------------------
--
2.25.4
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
