]> git.ipfire.org Git - thirdparty/mdadm.git/commit
UT FIX: imsm container can have different blocks number
authorAdam Kwolek <adam.kwolek@intel.com>
Tue, 8 Feb 2011 13:30:45 +0000 (14:30 +0100)
committerNeilBrown <neilb@suse.de>
Wed, 9 Feb 2011 02:47:55 +0000 (13:47 +1100)
commit8200f09e8fad8f67cc0f1231b4967ea373b0d56c
tree441eb277f52912192acd2d3f1dfa37946c7d57be
parente7ff7e4092dc9bd94bf9e50223061ecbf8b37e90
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>
tests/env-imsm-template