summaryrefslogtreecommitdiff
path: root/tests/env-imsm-template
diff options
context:
space:
mode:
authorAdam Kwolek <adam.kwolek@intel.com>2011-02-08 14:30:45 +0100
committerNeilBrown <neilb@suse.de>2011-02-09 13:47:55 +1100
commit8200f09e8fad8f67cc0f1231b4967ea373b0d56c (patch)
tree441eb277f52912192acd2d3f1dfa37946c7d57be /tests/env-imsm-template
parente7ff7e4092dc9bd94bf9e50223061ecbf8b37e90 (diff)
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 <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'tests/env-imsm-template')
-rw-r--r--tests/env-imsm-template2
1 files changed, 1 insertions, 1 deletions
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 )