All of
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <>
Subject: [PATCH 1/2] generic/223: make sure all files get created on the data device
Date: Tue, 20 Apr 2021 17:22:25 -0700	[thread overview]
Message-ID: <161896454559.776190.1857804198421552259.stgit@magnolia> (raw)
In-Reply-To: <161896453944.776190.2831340458112794975.stgit@magnolia>

From: Darrick J. Wong <>

This test formats filesystems with various stripe alignments, then
checks that data file allocations are actually aligned to those stripe
geometries.  If this test is run on an XFS filesystem with a realtime
volume and RTINHERIT is set on the root dir, the test will fail because
all new files will be created as realtime files, and realtime
allocations are not subject to data device stripe alignments.  Fix this
by clearing rtinherit on the root dir.

Signed-off-by: Darrick J. Wong <>
 tests/generic/223 |    5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tests/generic/223 b/tests/generic/223
index 1f85efe5..f6393293 100755
--- a/tests/generic/223
+++ b/tests/generic/223
@@ -43,6 +43,11 @@ for SUNIT_K in 8 16 32 64 128; do
 	_scratch_mkfs_geom $SUNIT_BYTES 4 $BLOCKSIZE >> $seqres.full 2>&1
+	# This test checks for stripe alignments of space allocations on the
+	# filesystem.  Make sure all files get created on the main device,
+	# which for XFS means no rt files.
+	test "$FSTYP" = "xfs" && $XFS_IO_PROG -c 'chattr -t' $SCRATCH_MNT
 	for SIZE_MULT in 1 2 8 64 256; do

  reply	other threads:[~2021-04-21  0:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  0:22 [PATCHSET 0/2] fstests: random fixes Darrick J. Wong
2021-04-21  0:22 ` Darrick J. Wong [this message]
2021-04-21 17:26   ` [PATCH 1/2] generic/223: make sure all files get created on the data device Brian Foster
2021-04-22  0:29   ` Allison Henderson
2021-04-21  0:22 ` [PATCH 2/2] common/dmthin: make this work with external log devices Darrick J. Wong
2021-04-21 17:26   ` Brian Foster
2021-04-22  0:29   ` Allison Henderson

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:

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

  git send-email \
    --in-reply-to=161896454559.776190.1857804198421552259.stgit@magnolia \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.