public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: cem@kernel.org
To: zlang@kernel.org
Cc: hch@lst.de, hans.holmberg@wdc.com, johannes.thumshirn@wdc.com,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: [PATCH 2/2] xfs: Add test for mkfs with smaller zone capacity
Date: Thu, 20 Nov 2025 17:08:30 +0100	[thread overview]
Message-ID: <20251120160901.63810-3-cem@kernel.org> (raw)
In-Reply-To: <20251120160901.63810-1-cem@kernel.org>

From: Carlos Maiolino <cem@kernel.org>

Add a regression test for initializing zoned block devices with
sequential zones with a capacity smaller than the conventional
zones capacity.

Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
---
 tests/xfs/333     | 37 +++++++++++++++++++++++++++++++++++++
 tests/xfs/333.out |  2 ++
 2 files changed, 39 insertions(+)
 create mode 100755 tests/xfs/333
 create mode 100644 tests/xfs/333.out

diff --git a/tests/xfs/333 b/tests/xfs/333
new file mode 100755
index 000000000000..f045b13c73ee
--- /dev/null
+++ b/tests/xfs/333
@@ -0,0 +1,37 @@
+#! /bin/bash
+# SPDX-License-Identifier: GPL-2.0
+# Copyright (c) 2025 Red Hat, Inc.  All Rights Reserved.
+#
+# FS QA Test 333
+#
+# Test that mkfs can properly initialize zoned devices
+# with a sequential zone capacity smaller than the conventional zone.
+#
+. ./common/preamble
+. ./common/zoned
+
+_begin_fstest auto zone mkfs quick
+_cleanup()
+{
+	_destroy_zloop $zloop
+}
+
+_require_scratch
+_require_zloop
+
+_scratch_mkfs > /dev/null 2>&1
+_scratch_mount >> $seqres.full
+
+zloopdir="$SCRATCH_MNT/zloop"
+zone_size=64
+conv_zones=2
+zone_capacity=63
+
+zloop=$(_create_zloop $zloopdir $zone_size $conv_zones $zone_capacity)
+
+_try_mkfs_dev $zloop >> $seqres.full 2>&1 || \
+	_fail "Cannot mkfs zoned filesystem"
+
+echo Silence is golden
+# success, all done
+_exit 0
diff --git a/tests/xfs/333.out b/tests/xfs/333.out
new file mode 100644
index 000000000000..60a158987a22
--- /dev/null
+++ b/tests/xfs/333.out
@@ -0,0 +1,2 @@
+QA output created by 333
+Silence is golden
-- 
2.51.1


  parent reply	other threads:[~2025-11-20 16:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 16:08 [PATCH 0/2] xfs: add regression test for small zone capacity cem
2025-11-20 16:08 ` [PATCH 1/2] common/zoned: enable passing a custom capacity cem
2025-11-21  6:46   ` Johannes Thumshirn
2025-11-21  6:50   ` Christoph Hellwig
2025-11-22  7:41   ` Zorro Lang
2025-11-20 16:08 ` cem [this message]
2025-11-21  6:51   ` [PATCH 2/2] xfs: Add test for mkfs with smaller zone capacity Christoph Hellwig
2025-11-21  6:51   ` Johannes Thumshirn
2025-11-21  6:57     ` hch
2025-11-21  7:00       ` Johannes Thumshirn
2025-11-21  8:34         ` Hans Holmberg
2025-11-24 15:27     ` Carlos Maiolino
2025-11-24 17:31       ` Johannes Thumshirn
2025-11-24 17:34         ` hch
2025-11-25 13:01         ` Carlos Maiolino
2025-11-22  8:36   ` Zorro Lang
2025-11-24 16:04     ` Carlos Maiolino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251120160901.63810-3-cem@kernel.org \
    --to=cem@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=hch@lst.de \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox