force_new_seq was used in some tests to avoid the
situation where the sequence from replay request
could be different than the one osp is at, due to
previous sequence width has been used up.
Now it can be handled so remvoe the force_new_seq
to speed up test runs.
Some force_new_seq are still required to make sure
there are enough objects in the current precreate pool
for the overstriping test cases.
Change-Id: Id1bc6760e721db61c11b1c3d6b2fa82965459728
Signed-off-by: Li Dongyang <dongyangli@ddn.com>
Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54433
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-by: Alex Zhuravlev <bzzz@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
# Exception is the test which need two separate nodes
CLIENT2=${CLIENT2:-$CLIENT1}
-force_new_seq_all
-
LU482_FAILED=$(mktemp -u $TMP/$TESTSUITE.lu482.XXXXXX)
test_0a() {
echo "Check file is LU482_FAILED=$LU482_FAILED"
$LFS setstripe $TDIR -i 0 -c 1
$LFS getstripe $TDIR
-force_new_seq_all
-
test_0a() {
zconf_umount $(hostname) $MOUNT -f
# needs to run during initial client->OST connection
assert_DIR
rm -rf $DIR/[df][0-9]* $DIR/f.$TESTSUITE.*
-force_new_seq_all
-
test_0a() { # was test_0
mkdir_on_mdt0 $DIR/$tdir || error "mkdir $DIR/$tdir failed"
replay_barrier $SINGLEMDS
cos_param_file=$TMP/rvbr-cos-params
save_lustre_params $(get_facets MDS) "mdt.*.commit_on_sharing" > $cos_param_file
-force_new_seq mds1
-
test_0a() {
local ver=$(get_version $CLIENT1 $DIR/$tdir/1a)