Lines Matching refs:message
9 the user can send a message to the target to start failing read
93 $ sudo dmsetup message dust1 0 addbadblock 60
96 $ sudo dmsetup message dust1 0 addbadblock 67
99 $ sudo dmsetup message dust1 0 addbadblock 72
111 To enable the "fail read on bad block" behavior, send the "enable" message::
113 $ sudo dmsetup message dust1 0 enable
144 result in an "Invalid argument" error, as well as a helpful message::
146 $ sudo dmsetup message dust1 0 addbadblock 88
147 device-mapper: message ioctl on dust1 failed: Invalid argument
151 result in an "Invalid argument" error, as well as a helpful message::
153 $ sudo dmsetup message dust1 0 removebadblock 87
154 device-mapper: message ioctl on dust1 failed: Invalid argument
161 following message command::
163 $ sudo dmsetup message dust1 0 countbadblocks
165 A message will print with the number of bad blocks currently
174 following message command::
176 $ sudo dmsetup message dust1 0 queryblock 72
178 The following message will print if the block is in the list::
182 The following message will print if the block is not in the list::
186 The "queryblock" message command will work in both the "enabled"
195 a "removebadblock" message command for every block), run the
196 following message command::
198 $ sudo dmsetup message dust1 0 clearbadblocks
200 After clearing the bad block list, the following message will appear::
204 If there were no bad blocks to clear, the following message will
213 with blocks 1 and 2 in the bad block list), run the following message
216 $ sudo dmsetup message dust1 0 listbadblocks
223 $ sudo dmsetup message dust1 0 listbadblocks
239 Single argument message commands::
260 This can be done by enabling "quiet mode" via the following message::
262 $ sudo dmsetup message dust1 0 quiet
266 message commands will still print in quiet mode.
273 To disable quiet mode, send the "quiet" message again::
275 $ sudo dmsetup message dust1 0 quiet