RFC introduce interface to list all badblocks
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | dm dust: add interface to list all badblocksdrivers/ | +21 | 1 reply | |
| 2/2 | dm dust: introduce listbadblocks in the rstDocumentation/ | +16 | 2 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Bryan Gurney |
|---|---|
| 1/2 | R-b |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC 0/2] introduce interface to list all badblocks
We can add/remove/query the badblocks, but no interface to list all badblocks when we want to know the badblocks we ever set still available. Add message listbadblocks to do this.
To list all bad block list, run the following message command:
$ sudo dmsetup message dust1 0 listbadblocks
We will get following message(image that we have insert block 1/2, and we will list the block index in order)::
device-mapper: dust: dust_list_badblocks: badblocks list as below:
device-mapper: dust: bad block: 1
device-mapper: dust: bad block: 2
device-mapper: dust: dust_list_badblocks: badblocks list end.
yangerkun (2):
dm dust: add interface to list all badblocks
dm dust: introduce listbadblocks in the rst
.../admin-guide/device-mapper/dm-dust.rst | 16 ++++++++++++++ drivers/md/dm-dust.c | 21 +++++++++++++++++++ 2 files changed, 37 insertions(+)
Signature · 1 line
2.25.4