diff options
| author | mwilck@arcor.de <mwilck@arcor.de> | 2013-09-14 23:24:07 +0200 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2013-10-16 15:29:43 +1100 |
| commit | 7bb1d61354e4f8932f0a6eb926d5855b05c8c7b8 (patch) | |
| tree | b308f63d9e76cf7cd9b03c00cf2f6a93e1ed8c82 /monitor.c | |
| parent | 7039479987745f19b166b1c28d45dfc41420e6d9 (diff) | |
Monitor: don't set arrays dirty after transition to read-only
This patch reverts commit 4867e068. Setting arrays dirty after
transition from inactive to anything else causes unnecessary
meta data writes and may wreak trouble unnecessarily when
a disk was missing during assembly but the array was never
written to.
The reason for 4867e068 was a special situation during reshape
from RAID0 to RAID4. I ran all IMSM test cases with it reverted
and found no regressions, so I believe the reshape logic for
IMSM works fine in mdadm 3.3 also without this.
Signed-off-by: Martin Wilck <mwilck@arcor.de>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'monitor.c')
| -rw-r--r-- | monitor.c | 7 |
1 files changed, 0 insertions, 7 deletions
@@ -270,13 +270,6 @@ static int read_and_act(struct active_array *a) a->info.resync_start ); - if (a->curr_state > inactive && - a->prev_state == inactive) { - /* array has been started - * possible that container operation has to be completed - */ - a->container->ss->set_array_state(a, 0); - } if ((a->curr_state == bad_word || a->curr_state <= inactive) && a->prev_state > inactive) { /* array has been stopped */ |