diff options
| author | NeilBrown <neilb@suse.de> | 2012-07-03 10:37:30 +1000 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2012-07-03 10:37:30 +1000 |
| commit | fc448a18ae6219af9a73257b1fbcd009efab4a81 (patch) | |
| tree | 4060ac0bb5a476696be56ae1d60b7242715baf46 /drivers/md | |
| parent | 6b16351acbd415e66ba16bf7d473ece1574cf0bc (diff) | |
| download | linux-3.10-fc448a18ae6219af9a73257b1fbcd009efab4a81.tar.gz linux-3.10-fc448a18ae6219af9a73257b1fbcd009efab4a81.tar.bz2 linux-3.10-fc448a18ae6219af9a73257b1fbcd009efab4a81.zip | |
md/raid10: Don't try to recovery unmatched (and unused) chunks.
If a RAID10 has an odd number of chunks - as might happen when there
are an odd number of devices - the last chunk has no pair and so is
not mirrored. We don't store data there, but when recovering the last
device in an array we retry to recover that last chunk from a
non-existent location. This results in an error, and the recovery
aborts.
When we get to that last chunk we should just stop - there is nothing
more to do anyway.
This bug has been present since the introduction of RAID10, so the
patch is appropriate for any -stable kernel.
Cc: stable@vger.kernel.org
Reported-by: Christian Balzer <chibi@gol.com>
Tested-by: Christian Balzer <chibi@gol.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md')
| -rw-r--r-- | drivers/md/raid10.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c index 99ae6068e45..bcf6ea8acc9 100644 --- a/drivers/md/raid10.c +++ b/drivers/md/raid10.c @@ -2890,6 +2890,12 @@ static sector_t sync_request(struct mddev *mddev, sector_t sector_nr, /* want to reconstruct this device */ rb2 = r10_bio; sect = raid10_find_virt(conf, sector_nr, i); + if (sect >= mddev->resync_max_sectors) { + /* last stripe is not complete - don't + * try to recover this sector. + */ + continue; + } /* Unless we are doing a full sync, or a replacement * we only need to recover the block if it is set in * the bitmap |