After the recent change in util-linux [1], the 'blkzone report' command no longer reports numeric values for write pointers when the write pointers are invalid. Instead, now it reports the sting 'N/A'. The test case zbd/002 assumed that 'blkzone report' command would return valid write pointer values for conventional zones. The test case worked before the blkzone change, but now the test fails because of the wrong assumption. To avoid the failure, do not check write pointer values when the zone type is conventional. Link: [1] https://github.com/util-linux/util-linux/commit/b032247f48d8b6a13bf8541eb663c779e448f568 Signed-off-by: Shin'ichiro Kawasaki --- tests/zbd/002 | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tests/zbd/002 b/tests/zbd/002 index 39c2ad5..cd9609d 100755 --- a/tests/zbd/002 +++ b/tests/zbd/002 @@ -80,7 +80,8 @@ _check_blkzone_report() { fi # Check write pointer - if ((cond != ZONE_COND_READ_ONLY && + if ((zone_type != ZONE_TYPE_CONVENTIONAL && + cond != ZONE_COND_READ_ONLY && cond != ZONE_COND_FULL && cond != ZONE_COND_OFFLINE && (wptr < 0 || wptr > len) )); then -- 2.53.0