From 8200f09e8fad8f67cc0f1231b4967ea373b0d56c Mon Sep 17 00:00:00 2001 From: Adam Kwolek Date: Tue, 8 Feb 2011 14:30:45 +0100 Subject: [PATCH] UT FIX: imsm container can have different blocks number When imsm container is created it have different blocks number in /proc/mdstat depending on containing array raid level (raid0/raid5). raid5 case: md127 : inactive sdd[3](S) sde[2](S) sdc[1](S) sdb[0](S) 2884 blocks super external:imsm raid0 case: md127 : inactive sdd[3](S) sde[2](S) sdc[1](S) sdb[0](S) 836 blocks super external:imsm Due to this, it cannot be compared to one value for both cases. Test imsm container existence before unit test run only. Signed-off-by: Adam Kwolek Signed-off-by: NeilBrown --- tests/env-imsm-template | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/env-imsm-template b/tests/env-imsm-template index 74c43c68..7a2890cd 100644 --- a/tests/env-imsm-template +++ b/tests/env-imsm-template @@ -2,7 +2,7 @@ imsm_check() { udevadm settle case $1 in container ) - grep -s "$(((418 * $2) / 2)) blocks super external:imsm" /proc/mdstat > /dev/null || { + grep -s "blocks super external:imsm" /proc/mdstat > /dev/null || { echo >&2 "**Fatal** Correctly formed container not found"; cat /proc/mdstat; exit 1; } ;; member ) -- 2.47.2