Whamcloud - gitweb
LU-3002 tests: Fix an OST index issue in replay-single
authorLi Wei <wei.g.li@intel.com>
Thu, 21 Mar 2013 07:55:16 +0000 (15:55 +0800)
committerOleg Drokin <oleg.drokin@intel.com>
Wed, 27 Mar 2013 22:02:56 +0000 (18:02 -0400)
commit9dabff0dc806cfb6a8de6e8bc27271425ba7261d
tree296a073f22d65e22b23ae2f01c67e5a5a2fa5a4f
parentc95b4c92009ebcf6361986d3973ae689d25d7c7a
LU-3002 tests: Fix an OST index issue in replay-single

When run with 16 OSTs, replay-single 90 happened to pick ost14 as
ostfail and complained:

  lfs find does not report the affected lustre-OST000d_UUID for fd

The "d" in "fd" is a hexadecimal OST index, taken from
"lustre-OST000d_UUID".  Because the actual file names use decimal OST
indices, the test failed to match the file "f13" with "fd".  Moreover,
the test assumes the OST index is a single-digit number, which may not
be case with more than 15 OSTs.  This patch changes the test to simply
calculate the index from the facet name.

Test-Parameters: ostcount=32 testlist=replay-single envdefinitions=ONLY=90
Change-Id: I0c95d28f83c41cabf4ed8e5ed618897d6000da3b
Signed-off-by: Li Wei <wei.g.li@intel.com>
Reviewed-on: http://review.whamcloud.com/5796
Tested-by: Hudson
Tested-by: Maloo <whamcloud.maloo@gmail.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Reviewed-by: wangdi <di.wang@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
lustre/tests/replay-single.sh