From: Anand Jain <anand.jain@oracle.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 10/10] btrfs: test tempfsid with device add, seed, and balance
Date: Thu, 29 Feb 2024 07:19:48 +0530 [thread overview]
Message-ID: <c5bf6886-252a-4614-a1be-25481d3776fa@oracle.com> (raw)
In-Reply-To: <CAL3q7H45T0+BHQqDwOTjWhWeG=yStY+x6EsznRrrdeGAE9qzng@mail.gmail.com>
>> +_require_btrfs_sysfs_fsid
>
> Same as in the previous test case. This requirement is not needed, the
> sysfs fsid path is not used anywhere in this test, likely copy-pasted
> from previous test cases in this patchset.
>
Yep. Replaced with "_require_btrfs_fs_feature temp_fsid"
>> diff --git a/tests/btrfs/315.out b/tests/btrfs/315.out
>> new file mode 100644
>> index 000000000000..56301f9f069e
>> --- /dev/null
>> +++ b/tests/btrfs/315.out
>> @@ -0,0 +1,10 @@
>> +QA output created by 315
>> +---- seed_device_must_fail ----
>> +mount: SCRATCH_MNT: WARNING: source write-protected, mounted read-only.
>> +mount: TEST_DIR/315/tempfsid_mnt: mount(2) system call failed: File exists.
The error output has changed due to some external fixes.
V4 contains changes accordingly.
Old:
mount: <mnt-point>: mount(2) system call failed: File exists.
New:
mount: <mnt-point>: fsconfig system call failed: File exists.
dmesg(1) may have more information after failed mount system call.
Thanks, Anand
prev parent reply other threads:[~2024-02-29 1:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 16:43 [PATCH v3 00/10] btrfs: functional test cases for tempfsid Anand Jain
2024-02-24 16:43 ` [PATCH v3 01/10] assign SCRATCH_DEV_POOL to an array Anand Jain
2024-02-24 16:43 ` [PATCH v3 02/10] btrfs: introduce tempfsid test group Anand Jain
2024-02-24 16:43 ` [PATCH v3 03/10] btrfs: create a helper function, check_fsid(), to verify the tempfsid Anand Jain
2024-02-26 11:47 ` Filipe Manana
2024-02-28 9:36 ` Anand Jain
2024-02-28 10:28 ` Filipe Manana
2024-02-29 1:50 ` Anand Jain
2024-02-24 16:43 ` [PATCH v3 04/10] btrfs: verify that subvolume mounts are unaffected by tempfsid Anand Jain
2024-02-26 11:49 ` Filipe Manana
2024-02-24 16:43 ` [PATCH v3 05/10] btrfs: check if cloned device mounts with tempfsid Anand Jain
2024-02-26 11:55 ` Filipe Manana
2024-02-29 1:49 ` Anand Jain
2024-02-24 16:43 ` [PATCH v3 06/10] btrfs: test case prerequisite _require_btrfs_mkfs_uuid_option Anand Jain
2024-02-24 16:43 ` [PATCH v3 07/10] btrfs: introduce helper for creating cloned devices with mkfs Anand Jain
2024-02-26 11:57 ` Filipe Manana
2024-02-24 16:43 ` [PATCH v3 08/10] btrfs: verify tempfsid clones using mkfs Anand Jain
2024-02-26 11:59 ` Filipe Manana
2024-02-24 16:43 ` [PATCH v3 09/10] btrfs: validate send-receive operation with tempfsid Anand Jain
2024-02-26 12:06 ` Filipe Manana
2024-02-29 1:49 ` Anand Jain
2024-02-24 16:43 ` [PATCH v3 10/10] btrfs: test tempfsid with device add, seed, and balance Anand Jain
2024-02-26 12:08 ` Filipe Manana
2024-02-29 1:49 ` Anand Jain [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=c5bf6886-252a-4614-a1be-25481d3776fa@oracle.com \
--to=anand.jain@oracle.com \
--cc=fdmanana@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.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