Re: [PATCH blktests] block/004: reset zones of TEST_DEV before fio operation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/4/23 14:20, Shin'ichiro Kawasaki wrote:
When test target is a zoned block device with max_active_zones limit
larger than max_open_zones, fio write operation may fail depending on
zone conditions. To avoid the failure, reset zones of the device before
the fio run.

Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@xxxxxxx>
---
  tests/block/004 | 6 +++++-
  1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/tests/block/004 b/tests/block/004
index 63484a4..52a260f 100755
--- a/tests/block/004
+++ b/tests/block/004
@@ -15,7 +15,10 @@ requires() {
  }
device_requires() {
-	! _test_dev_is_zoned || _have_fio_zbd_zonemode
+	if _test_dev_is_zoned; then
+		_have_fio_zbd_zonemode
+		_have_program blkzone
+	fi
  }
What would be the return value here?
Do we care?
Should we make it explicit?

Cheers,

Hannes
--
Dr. Hannes Reinecke		           Kernel Storage Architect
hare@xxxxxxx			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg
Managing Directors: I. Totev, A. Myers, A. McDonald, M. B. Moerman
(HRB 36809, AG Nürnberg)




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux