The test case zbd/006 performs random writes to the first sequential
write required zone of the test target zoned block device. To prepare
for this operation, it invokes the blkzone reset command, specifying the
offset of the test target zone. However, the zone count option is not
specified to the command. This resulted in reset of all sequential write
required zones on the device. This zone reset operation is unnecessary
for zones other than the first one and significantly increases the
operation time.
To address this issue, add the zone count option to the blkzone reset
command. Additionally, use long option names for better readability and
clarity.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@xxxxxxx>
---
tests/zbd/006 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/zbd/006 b/tests/zbd/006
index 2db0e9b..c47f81e 100755
--- a/tests/zbd/006
+++ b/tests/zbd/006
@@ -36,7 +36,8 @@ test_device() {
offset=$((ZONE_STARTS[zone_idx] * 512))
size=$((ZONE_LENGTHS[zone_idx] * 512))
- blkzone reset -o "${ZONE_STARTS[zone_idx]}" "${TEST_DEV}"
+ blkzone reset --offset "${ZONE_STARTS[zone_idx]}" --count 1 \
+ "${TEST_DEV}"
_test_dev_set_scheduler deadline
--
2.49.0
