d/numam-spdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
numam-spdk/test/ocf/common.sh

20 lines
493 B
Bash
Raw Normal View History

test/ocf: factor out common functions Move code like nvme_cfg and clean_nvme to a new file - test/ocf/common.sh Change-Id: Ife00cd979857ce69949ce9c9d9ad0b5581bb382b Signed-off-by: Vitaliy Mysak <vitaliy.mysak@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1629 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Michal Berger <michalx.berger@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-04-01 17:06:17 +02:00
source $rootdir/scripts/common.sh
source $rootdir/test/common/autotest_common.sh
rpc_py=$rootdir/scripts/rpc.py
check_format: Reformat the Bash code in compliance with shfmt Change-Id: I93e7b9d355870b0528a0ac3382fba1a10a558d45 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1718 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-05-07 13:27:06 +02:00
function clear_nvme() {
test/ocf: do not use iter_pci_class_code in OCF test See commit msg from db43b387: "Do not use iter_pci_class_code function in tests to iterate over NVMe drives. This function can return drives which at the moment of execution can not be whitelisted for use. This can result in test errors (such as simply bdev_nvme_attach_controller RPC command failing) or even using and deleting data from NVMe drive which was not meant to be used in tests." Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ifa70a51822f78e95b6cddbfe665ea95ec1b423c1 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2837 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-06-09 09:06:02 -04:00
mapfile -t bdf < <(get_first_nvme_bdf)
test/ocf: factor out common functions Move code like nvme_cfg and clean_nvme to a new file - test/ocf/common.sh Change-Id: Ife00cd979857ce69949ce9c9d9ad0b5581bb382b Signed-off-by: Vitaliy Mysak <vitaliy.mysak@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1629 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Michal Berger <michalx.berger@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-04-01 17:06:17 +02:00
# Clear metadata on NVMe device
$rootdir/scripts/setup.sh reset
test/ocf: Don't depend on gen_nvme.sh while detecting nvme ctrls gen_nvme.sh requires that all the nvme devices are not bound to the nvme driver which doesn't have to be the case when clear_nvme() is called. To not depend on which driver is in use, simply iterate over pci bus to find a proper device. This avoids additional setup.sh ping-pong which is required to make use of gen_nvme.sh. Additionally, upon exiting, in case mounts for given nvme device were detected, keep the test environment reset to leave nvmes bound to the nvme driver. Change-Id: I428c5e2b0517553d267411a30316bde5d1ce8eef Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1843 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2020-04-14 14:27:34 +02:00
name=$(get_nvme_name_from_bdf "${bdf[0]}")
test/ocf: factor out common functions Move code like nvme_cfg and clean_nvme to a new file - test/ocf/common.sh Change-Id: Ife00cd979857ce69949ce9c9d9ad0b5581bb382b Signed-off-by: Vitaliy Mysak <vitaliy.mysak@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1629 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Michal Berger <michalx.berger@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-04-01 17:06:17 +02:00
mountpoints=$(lsblk /dev/$name --output MOUNTPOINT -n | wc -w)
if [ "$mountpoints" != "0" ]; then
exit 1
fi
dd if=/dev/zero of=/dev/$name bs=1M count=1000 oflag=direct
$rootdir/scripts/setup.sh
}
Reference in New Issue Copy Permalink