From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com, zlang@redhat.com
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCH 3/3] xfs/216: handle larger log sizes
Date: Mon, 11 Apr 2022 15:55:13 -0700 [thread overview]
Message-ID: <164971771391.170109.16368399851366024102.stgit@magnolia> (raw)
In-Reply-To: <164971769710.170109.8985299417765876269.stgit@magnolia>
From: Darrick J. Wong <djwong@kernel.org>
mkfs will soon refuse to format a log smaller than 64MB, so update this
test to reflect the new log sizing calculations.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
tests/xfs/216.out | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/tests/xfs/216.out b/tests/xfs/216.out
index cbd7b652..3c12085f 100644
--- a/tests/xfs/216.out
+++ b/tests/xfs/216.out
@@ -1,10 +1,10 @@
QA output created by 216
-fssize=1g log =internal log bsize=4096 blocks=2560, version=2
-fssize=2g log =internal log bsize=4096 blocks=2560, version=2
-fssize=4g log =internal log bsize=4096 blocks=2560, version=2
-fssize=8g log =internal log bsize=4096 blocks=2560, version=2
-fssize=16g log =internal log bsize=4096 blocks=2560, version=2
-fssize=32g log =internal log bsize=4096 blocks=4096, version=2
-fssize=64g log =internal log bsize=4096 blocks=8192, version=2
+fssize=1g log =internal log bsize=4096 blocks=16384, version=2
+fssize=2g log =internal log bsize=4096 blocks=16384, version=2
+fssize=4g log =internal log bsize=4096 blocks=16384, version=2
+fssize=8g log =internal log bsize=4096 blocks=16384, version=2
+fssize=16g log =internal log bsize=4096 blocks=16384, version=2
+fssize=32g log =internal log bsize=4096 blocks=16384, version=2
+fssize=64g log =internal log bsize=4096 blocks=16384, version=2
fssize=128g log =internal log bsize=4096 blocks=16384, version=2
fssize=256g log =internal log bsize=4096 blocks=32768, version=2
next prev parent reply other threads:[~2022-04-11 22:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 22:54 [PATCHSET 0/3] fstests: updates for xfsprogs 5.15 Darrick J. Wong
2022-04-11 22:55 ` [PATCH 1/3] common/rc: let xfs_scrub tell us about its unicode checker Darrick J. Wong
2022-04-13 18:07 ` Zorro Lang
2022-04-11 22:55 ` [PATCH 2/3] xfs: test mkfs.xfs config file stack corruption issues Darrick J. Wong
2022-04-13 17:56 ` Zorro Lang
2022-04-11 22:55 ` Darrick J. Wong [this message]
2022-04-13 17:44 ` [PATCH 3/3] xfs/216: handle larger log sizes Zorro Lang
2022-04-14 1:51 ` Darrick J. Wong
2022-04-14 19:25 ` Zorro Lang
2022-04-14 19:36 ` Darrick J. Wong
2022-04-15 3:24 ` Zorro Lang
2022-04-15 15:04 ` [PATCH v1.1 " Darrick J. Wong
2022-04-16 13:35 ` Zorro Lang
2022-04-17 14:42 ` Eryu Guan
2022-04-17 16:39 ` Zorro Lang
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=164971771391.170109.16368399851366024102.stgit@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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 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.