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 09/12] btrfs: introduce helper for creating cloned devices with mkfs
Date: Sat, 17 Feb 2024 10:01:04 +0530 [thread overview]
Message-ID: <72e7772b-5e06-4393-b252-003237e839ed@oracle.com> (raw)
In-Reply-To: <CAL3q7H5fp8=SBeAbkmaJahTYCZQ5LQtbkcXR_2d1tXmhJ_Q87A@mail.gmail.com>
On 2/15/24 18:12, Filipe Manana wrote:
> On Thu, Feb 15, 2024 at 6:37 AM Anand Jain <anand.jain@oracle.com> wrote:
>>
>> Use newer mkfs.btrfs option to generate two cloned devices,
>> used in test cases.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> common/btrfs | 24 ++++++++++++++++++------
>> 1 file changed, 18 insertions(+), 6 deletions(-)
>>
>> diff --git a/common/btrfs b/common/btrfs
>> index 9a7fa2c71ec5..8ffce3c39695 100644
>> --- a/common/btrfs
>> +++ b/common/btrfs
>> @@ -91,13 +91,7 @@ _require_btrfs_mkfs_feature()
>> _require_btrfs_mkfs_uuid_option()
>> {
>> local cnt
>> - local feature
>>
>> - if [ -z $1 ]; then
>> - echo "Missing option name argument for _require_btrfs_mkfs_option"
>> - exit 1
>> - fi
>> - feature=$1
>
> This is confusing... It was just introduced in the previous patch that
> introduced this function (_require_btrfs_mkfs_uuid_option).
>
> If there was never any need for this code, why was it added in the
> previous patch and removed in this one, without any users in between?
>
This change was mistakenly introduced here; it should have been in
the previous patch. I will move it. Thx.
>> cnt=$($MKFS_BTRFS_PROG --help 2>&1 |grep -E --count "\-\-uuid|\-\-device-uuid")
>> if [ $cnt != 2 ]; then
>> _notrun "Require $MKFS_BTRFS_PROG with --uuid and --device-uuid option"
>> @@ -864,3 +858,21 @@ create_cloned_devices()
>> _fail "dd failed: $?"
>> echo done
>> }
>> +
>> +mkfs_clone()
>> +{
>> + local dev1=$1
>> + local dev2=$2
>> +
>> + [[ -z $dev1 || -z $dev2 ]] && \
>> + _fail "BUGGY code, mkfs_clone needs arg1 arg2"
>
> Rather more clear and informative to say "mkfs_clone requires two
> devices as arguments".
Sure.
>
>> +
>> + _mkfs_dev -fq $dev1
>> +
>> + fsid=$($BTRFS_UTIL_PROG inspect-internal dump-super $dev1 | \
>> + grep -E ^fsid | $AWK_PROG '{print $2}')
>> + uuid=$($BTRFS_UTIL_PROG inspect-internal dump-super $dev1 | \
>> + grep -E ^dev_item.uuid | $AWK_PROG '{print $2}')
>
> Make the variables local please.
>
Sure.
Thanks, Anand
> Thanks.
>
>> +
>> + _mkfs_dev -fq --uuid $fsid --device-uuid $uuid $dev2
>> +}
>> --
>> 2.39.3
>>
>>
next prev parent reply other threads:[~2024-02-17 4:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 6:34 [PATCH 00/12] btrfs: functional test cases for tempfsid Anand Jain
2024-02-15 6:34 ` [PATCH 01/12] add t_reflink_read_race to .gitignore file Anand Jain
2024-02-15 11:45 ` Filipe Manana
2024-02-15 11:50 ` Anand Jain
2024-02-15 6:34 ` [PATCH 02/12] assign SCRATCH_DEV_POOL to an array Anand Jain
2024-02-15 11:55 ` Filipe Manana
2024-02-15 6:34 ` [PATCH 03/12] btrfs: introduce tempfsid test group Anand Jain
2024-02-15 11:57 ` Filipe Manana
2024-02-15 6:34 ` [PATCH 04/12] btrfs: create a helper function, check_fsid(), to verify the tempfsid Anand Jain
2024-02-15 12:13 ` Filipe Manana
2024-02-16 15:02 ` Zorro Lang
2024-02-15 6:34 ` [PATCH 05/12] btrfs: verify that subvolume mounts are unaffected by tempfsid Anand Jain
2024-02-15 12:20 ` Filipe Manana
2024-02-15 6:34 ` [PATCH 06/12] create a helper to clone devices Anand Jain
2024-02-15 12:27 ` Filipe Manana
2024-02-15 6:34 ` [PATCH 07/12] btrfs: check if cloned device mounts with tempfsid Anand Jain
2024-02-15 12:33 ` Filipe Manana
2024-02-15 6:34 ` [PATCH 08/12] btrfs: test case prerequisite _require_btrfs_mkfs_uuid_option Anand Jain
2024-02-15 12:37 ` Filipe Manana
2024-02-15 6:34 ` [PATCH 09/12] btrfs: introduce helper for creating cloned devices with mkfs Anand Jain
2024-02-15 12:42 ` Filipe Manana
2024-02-17 4:31 ` Anand Jain [this message]
2024-02-15 6:34 ` [PATCH 10/12] btrfs: verify tempfsid clones using mkfs Anand Jain
2024-02-15 12:46 ` Filipe Manana
2024-02-15 6:34 ` [PATCH 11/12] btrfs: validate send-receive operation with tempfsid Anand Jain
2024-02-15 12:56 ` Filipe Manana
2024-02-15 6:34 ` [PATCH 12/12] btrfs: test tempfsid with device add, seed, and balance Anand Jain
2024-02-15 13:03 ` Filipe Manana
2024-02-19 13:18 ` Anand Jain
2024-02-19 13:29 ` Filipe Manana
2024-02-19 13:33 ` Anand Jain
2024-02-19 19:47 ` [PATCH 00/12] btrfs: functional test cases for tempfsid Anand Jain
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=72e7772b-5e06-4393-b252-003237e839ed@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