Move the sanity.sh test_255a version check to the start of the test
instead of after some of the ladvise functionality is tested.
That said, there is still an issue here, because the client shouldn't
hang indefinitely if the server is returning -EOPNOTSUPP, in the case
where a new client/lfs is connecting to an old OSS, and that issue is
not addressed by this patch.
Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
Change-Id: If1fbc13bd60cfc1942a43aff40e3e7905cdcab07
Reviewed-on: https://review.whamcloud.com/25362
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Saurabh Tandan <saurabh.tandan@intel.com>
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
}
test_255a() {
+ [ $(lustre_version_code ost1) -lt $(version_code 2.8.54) ] &&
+ skip "lustre < 2.8.54 does not support ladvise " && return
+
lfs setstripe -c -1 -i 0 $DIR/$tfile || error "$tfile failed"
ladvise_no_type willread $DIR/$tfile &&
ladvise_no_ioctl $DIR/$tfile &&
skip "ladvise ioctl is not supported" && return
- [ $(lustre_version_code ost1) -lt $(version_code 2.8.54) ] &&
- skip "lustre < 2.8.54 does not support ladvise " && return
-
local size_mb=100
local size=$((size_mb * 1048576))
dd if=/dev/zero of=$DIR/$tfile bs=1048576 count=$size_mb ||