Lines Matching full:blocks

10 requests on specific blocks (to emulate the behavior of a hard disk
14 "dmsetup status" displays "fail_read_on_bad_block"), reads of blocks
17 Writes of blocks in the "bad block list will result in the following:
28 messages to add arbitrary bad blocks at new locations, and the
30 configured "bad blocks" will be treated as bad, or bypassed.
86 Adding and removing bad blocks
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".
128 ...and writing to the bad blocks will remove the blocks from the list,
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
204 If there were no bad blocks to clear, the following message will
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
230 Operations on blocks (requires a <blknum> argument)::
258 On test runs with many bad blocks, it may be desirable to avoid
259 excessive logging (from bad blocks added, removed, or "remapped").