Re: [md PATCH 07/36] md/raid1: avoid reading known bad blocks during resync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



NeilBrown <neilb@xxxxxxx> writes:

> 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: NeilBrown <neilb@xxxxxxx>

Reviewed-by: Namhyung Kim <namhyung@xxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux