Lines Matching full:dust

1 dm-dust
27 With dm-dust, the user can use the "addbadblock" and "removebadblock"
58 Create the dm-dust device:
63         $ sudo dmsetup create dust1 --table '0 33552384 dust /dev/vdb1 0 512'
69         $ sudo dmsetup create dust1 --table '0 33552384 dust /dev/vdb1 0 4096'
76         0 33552384 dust 252:17 bypass verbose
94         kernel: device-mapper: dust: badblock added at block 60
97         kernel: device-mapper: dust: badblock added at block 67
100         kernel: device-mapper: dust: badblock added at block 72
106         0 33552384 dust 252:17 bypass
114         kernel: device-mapper: dust: enabling read failures on bad sectors
117         0 33552384 dust 252:17 fail_read_on_bad_block
135         kernel: device-mapper: dust: block 60 removed from badblocklist by write
136         kernel: device-mapper: dust: block 67 removed from badblocklist by write
137         kernel: device-mapper: dust: block 72 removed from badblocklist by write
138         kernel: device-mapper: dust: block 87 removed from badblocklist by write
148         kernel: device-mapper: dust: block 88 already in badblocklist
155         kernel: device-mapper: dust: block 87 not found in badblocklist
228 Below is a list of the messages that can be sent to a dust device:
271         0 33552384 dust 252:17 fail_read_on_bad_block quiet
278         0 33552384 dust 252:17 fail_read_on_bad_block verbose