From: Thomas Bertschinger <tahbertschinger@gmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
bfoster@redhat.com, linux-fsdevel@vger.kernel.org,
sandeen@redhat.com, dhowells@redhat.com
Cc: Thomas Bertschinger <tahbertschinger@gmail.com>
Subject: [PATCH KTEST] add test to exercise the new mount API for bcachefs
Date: Mon, 27 May 2024 22:36:12 -0600 [thread overview]
Message-ID: <20240528043612.812644-5-tahbertschinger@gmail.com> (raw)
In-Reply-To: <20240528043612.812644-1-tahbertschinger@gmail.com>
Signed-off-by: Thomas Bertschinger <tahbertschinger@gmail.com>
---
tests/bcachefs/single_device.ktest | 33 ++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/tests/bcachefs/single_device.ktest b/tests/bcachefs/single_device.ktest
index 7476a08..e170b8b 100755
--- a/tests/bcachefs/single_device.ktest
+++ b/tests/bcachefs/single_device.ktest
@@ -79,6 +79,39 @@ test_remount_ro_rw()
check_counters ${ktest_scratch_dev[0]}
}
+test_mount_options()
+{
+ local dev=${ktest_scratch_dev[0]}
+ set_watchdog 10
+
+ run_quiet "" bcachefs format -f --errors=panic $dev
+
+ echo "test: valid mount options"
+ mount -t bcachefs -o metadata_checksum=crc64,metadata_target=$(basename $dev) $dev /mnt
+ mount -t bcachefs | grep --quiet metadata_checksum
+ mount -t bcachefs | grep --quiet metadata_target
+
+ echo "test: valid remount options"
+ mount -o remount,ro,errors=continue /mnt
+ mount -t bcachefs | grep --quiet metadata_target
+ mount -t bcachefs | grep --quiet continue
+ mount -t bcachefs | grep --quiet ro
+ umount /mnt
+
+ echo "test: invalid mount options"
+ ! mount -t bcachefs -o metadata_checksum=invalid $dev /mnt
+ ! mount -t bcachefs -o promote_target=$(basename $dev),metadata_target=not_a_device $dev /mnt
+
+ echo "test: invalid remount options"
+ mount -t bcachefs $dev /mnt
+ ! mount -o remount,promote_target=not_a_device /mnt
+ ! mount -o remount,metadata_replicas=not_a_number /mnt
+ umount /mnt
+
+ bcachefs fsck -ny $dev
+ check_counters $dev
+}
+
test_extent_merge2()
{
local p=/sys/module/bcachefs/parameters/debug_check_iterators
--
2.45.0
prev parent reply other threads:[~2024-05-28 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 4:36 [PATCH 0/3] use new mount API for bcachefs Thomas Bertschinger
2024-05-28 4:36 ` [PATCH 1/3] bcachefs: add printbuf arg to bch2_parse_mount_opts() Thomas Bertschinger
2024-05-28 4:36 ` [PATCH 2/3] bcachefs: Add error code to defer option parsing Thomas Bertschinger
2024-05-28 4:36 ` [PATCH 3/3] bcachefs: use new mount API Thomas Bertschinger
2024-05-28 4:36 ` Thomas Bertschinger [this message]
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=20240528043612.812644-5-tahbertschinger@gmail.com \
--to=tahbertschinger@gmail.com \
--cc=bfoster@redhat.com \
--cc=dhowells@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).