diff options
| author | Heinz Mauelshagen <heinzm@redhat.com> | 2016-08-03 22:57:49 +0200 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2016-08-04 10:05:30 -0400 |
| commit | 2a034ec197aa574dd159961cc661c9b08cd76425 (patch) | |
| tree | a911d8afaba0c54858e1de2e01ea6f910d3446ba | |
| parent | b2a4872a45280217149324e3bbef228cd5a0a270 (diff) | |
| download | linux-2a034ec197aa574dd159961cc661c9b08cd76425.tar.bz2 | |
dm raid: fix use of wrong status char during resynchronization
During a resynchronization, device status char 'a' is output on the raid
status line for every device of a RAID set. It changes from 'a' to 'A'
(unless device failure) when the resynchronization completes.
Interrupting and restarting a resynchronization, by reloading the DM
table, erroneously lead to status char 'A'.
Fix this by avoiding setting the MD_RECOVERY_REQUESTED flag in
raid_preresume().
Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
| -rw-r--r-- | drivers/md/dm-raid.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/md/dm-raid.c b/drivers/md/dm-raid.c index 7b403ab41bd3..1b9795d75ef8 100644 --- a/drivers/md/dm-raid.c +++ b/drivers/md/dm-raid.c @@ -3578,7 +3578,6 @@ static int raid_preresume(struct dm_target *ti) /* Be prepared for mddev_resume() in raid_resume() */ set_bit(MD_RECOVERY_FROZEN, &mddev->recovery); if (mddev->recovery_cp && mddev->recovery_cp < MaxSector) { - set_bit(MD_RECOVERY_REQUESTED, &mddev->recovery); set_bit(MD_RECOVERY_SYNC, &mddev->recovery); mddev->resync_min = mddev->recovery_cp; } |