[PATCH] FIX: After discarding array give chance monitor to remove it

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

 



When raid0 expansion occurs, takeover operation is used.
After backward takeover monitor remains in memory.

This happens due to remaining just removed active array in mdmon structures.
If there is no other monitored arrays, mdmon has to finish his work.

Problem was introduced in patch (2011.03.22):
    mdmon: Stop keeping track of RAID0 (and LINEAR) arrays.
Prior to this patch mdmon kicking occurs via replace_array() where
wakeup_monitor() was called.

Signed-off-by: Adam Kwolek <adam.kwolek@xxxxxxxxx>
---

 managemon.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/managemon.c b/managemon.c
index 67c5951..6662f67 100644
--- a/managemon.c
+++ b/managemon.c
@@ -462,6 +462,7 @@ static void manage_member(struct mdstat_ent *mdstat,
 		int level = map_name(pers, mdstat->level);
 		if (level == 0 || level == LEVEL_LINEAR) {
 			a->container = NULL;
+			wakeup_monitor();
 			return;
 		}
 		else if (a->info.array.level != level && level > 0) {

--
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