Lines Matching refs:message

9 the user can send a message to the target to start failing read
79 $ sudo dmsetup message dust1 0 addbadblock 60
82 $ sudo dmsetup message dust1 0 addbadblock 67
85 $ sudo dmsetup message dust1 0 addbadblock 72
97 To enable the "fail read on bad block" behavior, send the "enable" message:
99 $ sudo dmsetup message dust1 0 enable
130 result in an "Invalid argument" error, as well as a helpful message:
132 $ sudo dmsetup message dust1 0 addbadblock 88
133 device-mapper: message ioctl on dust1  failed: Invalid argument
137 result in an "Invalid argument" error, as well as a helpful message:
139 $ sudo dmsetup message dust1 0 removebadblock 87
140 device-mapper: message ioctl on dust1  failed: Invalid argument
147 following message command:
149 $ sudo dmsetup message dust1 0 countbadblocks
151 A message will print with the number of bad blocks currently
160 following message command:
162 $ sudo dmsetup message dust1 0 queryblock 72
164 The following message will print if the block is in the list:
167 The following message will print if the block is in the list:
170 The "queryblock" message command will work in both the "enabled"
179 a "removebadblock" message command for every block), run the
180 following message command:
182 $ sudo dmsetup message dust1 0 clearbadblocks
184 After clearing the bad block list, the following message will appear:
188 If there were no bad blocks to clear, the following message will
207 Single argument message commands:
227 This can be done by enabling "quiet mode" via the following message:
229 $ sudo dmsetup message dust1 0 quiet
233 message commands will still print in quiet mode.
240 To disable quiet mode, send the "quiet" message again:
242 $ sudo dmsetup message dust1 0 quiet