[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-raid
Subject:    [PATCH] FIX: After discarding array give chance monitor to remove it
From:       Adam Kwolek <adam.kwolek () intel ! com>
Date:       2011-03-28 11:56:49
Message-ID: 20110328115648.13950.11803.stgit () gklab-128-013 ! igk ! intel ! com
[Download RAW message or body]

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@intel.com>
---

 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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]