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.
72 Adding and removing bad blocks:
75 At any time (i.e.: whether the device has the "bad block" emulation
76 enabled or disabled), bad blocks may be added or removed from the
88 These bad blocks will be stored in the "bad block list".
97 To enable the "fail read on bad block" behavior, send the "enable" message:
100 kernel: device-mapper: dust: enabling read failures on bad sectors
105 With the device in "fail read on bad block" mode, attempting to read a
114 ...and writing to the bad blocks will remove the blocks from the list,
126 Bad block add/remove error handling:
129 Attempting to add a bad block that already exists in the list will
136 Attempting to remove a bad block that doesn't exist in the list will
143 Counting the number of bad blocks in the bad block list:
146 To count the number of bad blocks configured in the device, run the
151 A message will print with the number of bad blocks currently
156 Querying for specific bad blocks:
159 To find out if a specific block is in the bad block list, run the
172 will be treated as "bad" without having to issue I/O to the device,
173 or having to "enable" the bad block emulation.
175 Clearing the bad block list:
178 To clear the bad block list (without needing to individually run
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
225 On test runs with many bad blocks, it may be desirable to avoid
226 excessive logging (from bad blocks added, removed, or "remapped").
260 When a bad sector occurs on a hard disk drive, reads to that sector
266 be bad sectors that occur on the device in the future, in a different,
270 of a bad sector at a known sector location, at a known time, based