Set safe_mode_delay to something >0, otherwise all container subarrays assembled will have safe_mode_delay=0. That will break the assumption that meta data becomes clean after running mdadm --wait-clean. Use the same value as in getinfo_super_ddf_bvd. It would be cleaner to call that directly from container_content_ddf, but I need to check possible side effects first. Signed-off-by: Martin Wilck <mwilck@xxxxxxxx> --- super-ddf.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/super-ddf.c b/super-ddf.c index 013bb9d..d8fa654 100644 --- a/super-ddf.c +++ b/super-ddf.c @@ -3668,6 +3668,7 @@ static struct mdinfo *container_content_ddf(struct supertype *st, char *subarray this->array.md_minor = -1; this->array.major_version = -1; this->array.minor_version = -2; + this->safe_mode_delay = 200; cptr = (__u32 *)(vc->conf.guid + 16); this->array.ctime = DECADE + __be32_to_cpu(*cptr); this->array.utime = DECADE + -- 1.7.3.4 -- 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
