Lines Matching full:bad

4 This target emulates the behavior of bad sectors at arbitrary
11 drive with bad sectors).
15 in the "bad block list" will fail with EIO ("Input/output error").
17 Writes of blocks in the "bad block list will result in the following:
19 1. Remove the block from the "bad block list".
22 This emulates the "remapped sector" behavior of a drive with bad
25 Normally, a drive that is encountering bad sectors will most likely
26 encounter more bad sectors, at an unknown time or location.
28 messages to add arbitrary bad blocks at new locations, and the
30 configured "bad blocks" will be treated as bad, or bypassed.
32 simulating a "failure" event where bad sectors start to appear.
73 bad block additions, removals, and remaps will be verbosely logged)::
86 Adding and removing bad blocks
89 At any time (i.e.: whether the device has the "bad block" emulation
90 enabled or disabled), bad blocks may be added or removed from the
102 These bad blocks will be stored in the "bad block list".
111 To enable the "fail read on bad block" behavior, send the "enable" message::
114         kernel: device-mapper: dust: enabling read failures on bad sectors
119 With the device in "fail read on bad block" mode, attempting to read a
128 ...and writing to the bad blocks will remove the blocks from the list,
140 Bad block add/remove error handling
143 Attempting to add a bad block that already exists in the list will
150 Attempting to remove a bad block that doesn't exist in the list will
157 Counting the number of bad blocks in the bad block list
160 To count the number of bad blocks configured in the device, run the
165 A message will print with the number of bad blocks currently
170 Querying for specific bad blocks
173 To find out if a specific block is in the bad block list, run the
188 will be treated as "bad" without having to issue I/O to the device,
189 or having to "enable" the bad block emulation.
191 Clearing the bad block list
194 To clear the bad block list (without needing to individually run
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
209 Listing the bad block list
212 To list all bad blocks in the bad block list (using an example device
213 with blocks 1 and 2 in the bad block list), run the following message
220 If there are no bad blocks in the bad block list, the command will
258 On test runs with many bad blocks, it may be desirable to avoid
259 excessive logging (from bad blocks added, removed, or "remapped").
293 When a bad sector occurs on a hard disk drive, reads to that sector
299 be bad sectors that occur on the device in the future, in a different,
303 of a bad sector at a known sector location, at a known time, based