1. 28 Jul, 2011 8 commits
    • NeilBrown's avatar
      md/raid1: avoid reading known bad blocks during resync · 06f60385
      NeilBrown authored
      When performing resync/etc, keep the size of the request
      small enough that it doesn't overlap any known bad blocks.
      Devices with badblocks at the start of the request are completely
      excluded.
      If there is nowhere to read from due to bad blocks, record
      a bad block on each target device.
      
      Now that we never read from known-bad-blocks we can allow devices with
      known-bad-blocks into a RAID1.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      06f60385
    • NeilBrown's avatar
      md/raid1: avoid reading from known bad blocks. · d2eb35ac
      NeilBrown authored
      Now that we have a bad block list, we should not read from those
      blocks.
      There are several main parts to this:
        1/ read_balance needs to check for bad blocks, and return not only
           the chosen device, but also how many good blocks are available
           there.
        2/ fix_read_error needs to avoid trying to read from bad blocks.
        3/ read submission must be ready to issue multiple reads to
           different devices as different bad blocks on different devices
           could mean that a single large read cannot be served by any one
           device, but can still be served by the array.
           This requires keeping count of the number of outstanding requests
           per bio.  This count is stored in 'bi_phys_segments'
        4/ retrying a read needs to also be ready to submit a smaller read
           and queue another request for the rest.
      
      This does not yet handle bad blocks when reading to perform resync,
      recovery, or check.
      
      'md_trim_bio' will also be used for RAID10, so put it in md.c and
      export it.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      d2eb35ac
    • NeilBrown's avatar
      md: Disable bad blocks and v0.90 metadata. · 9f2f3830
      NeilBrown authored
      v0.90 metadata cannot record bad blocks, so when loading metadata
      for such a device, set shift to -1.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      9f2f3830
    • NeilBrown's avatar
      md: load/store badblock list from v1.x metadata · 2699b672
      NeilBrown authored
      Space must have been allocated when array was created.
      A feature flag is set when the badblock list is non-empty, to
      ensure old kernels don't load and trust the whole device.
      
      We only update the on-disk badblocklist when it has changed.
      If the badblocklist (or other metadata) is stored on a bad block, we
      don't cope very well.
      
      If metadata has no room for bad block, flag bad-blocks as disabled,
      and do the same for 0.90 metadata.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      2699b672
    • NeilBrown's avatar
      md: don't allow arrays to contain devices with bad blocks. · 34b343cf
      NeilBrown authored
      As no personality understand bad block lists yet, we must
      reject any device that is known to contain bad blocks.
      As the personalities get taught, these tests can be removed.
      
      This only applies to raid1/raid5/raid10.
      For linear/raid0/multipath/faulty the whole concept of bad blocks
      doesn't mean anything so there is no point adding the checks.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      Reviewed-by: default avatarNamhyung Kim <namhyung@gmail.com>
      34b343cf
    • Namhyung Kim's avatar
      md: add documentation for bad block log · 6e0d2d03
      Namhyung Kim authored
      Previous patch in the bad block series added new sysfs interfaces
      ([unacknowledged_]bad_blocks) for each rdev without documentation.
      Add it.
      Signed-off-by: default avatarNamhyung Kim <namhyung@gmail.com>
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      6e0d2d03
    • NeilBrown's avatar
      md/bad-block-log: add sysfs interface for accessing bad-block-log. · 16c791a5
      NeilBrown authored
      This can show the log (providing it fits in one page) and
      allows bad blocks to be 'acknowledged' meaning that they
      have safely been recorded in metadata.
      
      Clearing bad blocks is not allowed via sysfs (except for
      code testing).  A bad block can only be cleared when
      a write to the block succeeds.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      Reviewed-by: default avatarNamhyung Kim <namhyung@gmail.com>
      16c791a5
    • NeilBrown's avatar
      md: beginnings of bad block management. · 2230dfe4
      NeilBrown authored
      This the first step in allowing md to track bad-blocks per-device so
      that we can fail individual blocks rather than the whole device.
      
      This patch just adds a data structure for recording bad blocks, with
      routines to add, remove, search the list.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      Reviewed-by: default avatarNamhyung Kim <namhyung@gmail.com>
      2230dfe4
  2. 27 Jul, 2011 25 commits
  3. 26 Jul, 2011 7 commits