From: Anand Jain <anand.jain@oracle.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org, zlang@redhat.com
Subject: Re: [PATCH v2 08/10] btrfs: verify tempfsid clones using mkfs
Date: Sat, 24 Feb 2024 17:11:55 +0530 [thread overview]
Message-ID: <7c51df13-796e-4d94-9d2b-dfadf7ffd7f6@oracle.com> (raw)
In-Reply-To: <CAL3q7H4Si2u730Lzk6gcX0WAvidNux9Zrtcvi9W4yKaPCj+93Q@mail.gmail.com>
On 2/20/24 22:25, Filipe Manana wrote:
> On Mon, Feb 19, 2024 at 7:50 PM Anand Jain <anand.jain@oracle.com> wrote:
>>
>> Create appearing to be a clone using the mkfs.btrfs option and test if
>> the tempfsid is active.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> v2:
>> Remove unnecessary function.
>> Add clone group
>> use $UMOUNT_PROG
>> Let _cp_reflink fail on the stdout.
>>
>> tests/btrfs/313 | 55 +++++++++++++++++++++++++++++++++++++++++++++
>> tests/btrfs/313.out | 16 +++++++++++++
>> 2 files changed, 71 insertions(+)
>> create mode 100755 tests/btrfs/313
>> create mode 100644 tests/btrfs/313.out
>>
>> diff --git a/tests/btrfs/313 b/tests/btrfs/313
>> new file mode 100755
>> index 000000000000..c495a770c212
>> --- /dev/null
>> +++ b/tests/btrfs/313
>> @@ -0,0 +1,55 @@
>> +#! /bin/bash
>> +# SPDX-License-Identifier: GPL-2.0
>> +# Copyright (c) 2024 Oracle. All Rights Reserved.
>> +#
>> +# FS QA Test 313
>> +#
>> +# Functional test for the tempfsid, clone devices created using the mkfs option.
>> +#
>> +. ./common/preamble
>> +_begin_fstest auto quick clone tempfsid
>> +
>> +_cleanup()
>> +{
>> + cd /
>> + $UMOUNT_PROG $mnt1 > /dev/null 2>&1
>> + rm -r -f $tmp.*
>> + rm -r -f $mnt1
>> +}
>> +
>> +. ./common/filter.btrfs
>> +. ./common/reflink
>> +
>> +_supported_fs btrfs
>> +_require_cp_reflink
>> +_require_btrfs_sysfs_fsid
>> +_require_scratch_dev_pool 2
>> +_require_btrfs_fs_feature temp_fsid
>> +_require_btrfs_command inspect-internal dump-super
>> +_require_btrfs_mkfs_uuid_option
>
> So same as before, these last 2 _require_* are because of the
> check_fsid() function,
Yes, they have already been checked in mkfs_clone(),
so they have been removed here.
Thanks.
> defined at common/btrfs, so they should be in the function and not
> spread over every test case that calls it.
>
> Thanks.
>
>> +
>> +_scratch_dev_pool_get 2
>> +
>> +mnt1=$TEST_DIR/$seq/mnt1
>> +mkdir -p $mnt1
>> +
>> +echo ---- clone_uuids_verify_tempfsid ----
>> +mkfs_clone ${SCRATCH_DEV_NAME[0]} ${SCRATCH_DEV_NAME[1]}
>> +
>> +echo Mounting original device
>> +_mount ${SCRATCH_DEV_NAME[0]} $SCRATCH_MNT
>> +check_fsid ${SCRATCH_DEV_NAME[0]}
>> +
>> +echo Mounting cloned device
>> +_mount ${SCRATCH_DEV_NAME[1]} $mnt1
>> +check_fsid ${SCRATCH_DEV_NAME[1]}
>> +
>> +$XFS_IO_PROG -fc 'pwrite -S 0x61 0 9000' $SCRATCH_MNT/foo | _filter_xfs_io
>> +echo cp reflink must fail
>> +_cp_reflink $SCRATCH_MNT/foo $mnt1/bar 2>&1 | _filter_testdir_and_scratch
>> +
>> +_scratch_dev_pool_put
>> +
>> +# success, all done
>> +status=0
>> +exit
>> diff --git a/tests/btrfs/313.out b/tests/btrfs/313.out
>> new file mode 100644
>> index 000000000000..7a089d2c29c5
>> --- /dev/null
>> +++ b/tests/btrfs/313.out
>> @@ -0,0 +1,16 @@
>> +QA output created by 313
>> +---- clone_uuids_verify_tempfsid ----
>> +Mounting original device
>> +On disk fsid: FSID
>> +Metadata uuid: FSID
>> +Temp fsid: FSID
>> +Tempfsid status: 0
>> +Mounting cloned device
>> +On disk fsid: FSID
>> +Metadata uuid: FSID
>> +Temp fsid: TEMPFSID
>> +Tempfsid status: 1
>> +wrote 9000/9000 bytes at offset 0
>> +XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
>> +cp reflink must fail
>> +cp: failed to clone 'TEST_DIR/313/mnt1/bar' from 'SCRATCH_MNT/foo': Invalid cross-device link
>> --
>> 2.39.3
>>
next prev parent reply other threads:[~2024-02-24 11:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 19:48 [PATCH v2 00/10] btrfs: functional test cases for tempfsid Anand Jain
2024-02-19 19:48 ` [PATCH v2 01/10] assign SCRATCH_DEV_POOL to an array Anand Jain
2024-02-20 16:17 ` Filipe Manana
2024-02-19 19:48 ` [PATCH v2 02/10] btrfs: introduce tempfsid test group Anand Jain
2024-02-19 19:48 ` [PATCH v2 03/10] btrfs: create a helper function, check_fsid(), to verify the tempfsid Anand Jain
2024-02-20 16:24 ` Filipe Manana
2024-02-19 19:48 ` [PATCH v2 04/10] btrfs: verify that subvolume mounts are unaffected by tempfsid Anand Jain
2024-02-20 16:30 ` Filipe Manana
2024-02-23 17:22 ` Anand Jain
2024-02-19 19:48 ` [PATCH v2 05/10] btrfs: check if cloned device mounts with tempfsid Anand Jain
2024-02-20 16:44 ` Filipe Manana
2024-02-23 17:35 ` Anand Jain
2024-02-19 19:48 ` [PATCH v2 06/10] btrfs: test case prerequisite _require_btrfs_mkfs_uuid_option Anand Jain
2024-02-20 16:47 ` Filipe Manana
2024-02-19 19:48 ` [PATCH v2 07/10] btrfs: introduce helper for creating cloned devices with mkfs Anand Jain
2024-02-20 16:51 ` Filipe Manana
2024-02-23 17:44 ` Anand Jain
2024-02-19 19:48 ` [PATCH v2 08/10] btrfs: verify tempfsid clones using mkfs Anand Jain
2024-02-20 16:55 ` Filipe Manana
2024-02-24 11:41 ` Anand Jain [this message]
2024-02-19 19:48 ` [PATCH v2 09/10] btrfs: validate send-receive operation with tempfsid Anand Jain
2024-02-20 16:57 ` Filipe Manana
2024-02-24 0:53 ` Anand Jain
2024-02-19 19:48 ` [PATCH v2 10/10] btrfs: test tempfsid with device add, seed, and balance Anand Jain
2024-02-20 17:05 ` Filipe Manana
2024-02-24 11:29 ` 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=7c51df13-796e-4d94-9d2b-dfadf7ffd7f6@oracle.com \
--to=anand.jain@oracle.com \
--cc=fdmanana@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox