diff options
| author | Nigel Croxon <ncroxon@redhat.com> | 2019-09-06 16:21:33 +0300 |
|---|---|---|
| committer | Song Liu <songliubraving@fb.com> | 2019-09-13 23:10:05 +0300 |
| commit | b76b4715eba0d0ed574f58918b29c1b2f0fa37a8 (patch) | |
| tree | af385c0975738ebfd5257d842d4225ad8edee99a /drivers/md/raid5.c | |
| parent | 21fa1004ff5d749c90cef77525b73a49ef5583dc (diff) | |
| download | linux-b76b4715eba0d0ed574f58918b29c1b2f0fa37a8.tar.xz | |
raid5: don't increment read_errors on EILSEQ return
While MD continues to count read errors returned by the lower layer.
If those errors are -EILSEQ, instead of -EIO, it should NOT increase
the read_errors count.
When RAID6 is set up on dm-integrity target that detects massive
corruption, the leg will be ejected from the array. Even if the
issue is correctable with a sector re-write and the array has
necessary redundancy to correct it.
The leg is ejected because it runs up the rdev->read_errors beyond
conf->max_nr_stripes. The return status in dm-drypt when there is
a data integrity error is -EILSEQ (BLK_STS_PROTECTION).
Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
Signed-off-by: Song Liu <songliubraving@fb.com>
Diffstat (limited to 'drivers/md/raid5.c')
| -rw-r--r-- | drivers/md/raid5.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index da6a86e28318..8ea8443e09d5 100644 --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -2526,7 +2526,8 @@ static void raid5_end_read_request(struct bio * bi) int set_bad = 0; clear_bit(R5_UPTODATE, &sh->dev[i].flags); - atomic_inc(&rdev->read_errors); + if (!(bi->bi_status == BLK_STS_PROTECTION)) + atomic_inc(&rdev->read_errors); if (test_bit(R5_ReadRepl, &sh->dev[i].flags)) pr_warn_ratelimited( "md/raid:%s: read error on replacement device (sector %llu on %s).\n", |