linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Dave Chinner <david@fromorbit.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] fstests: add configuration option for executing post mkfs commands
Date: Mon, 9 Oct 2023 17:48:49 +0530	[thread overview]
Message-ID: <d4e7ba14-dc94-4611-8f7d-e3c5aafe80e1@oracle.com> (raw)
In-Reply-To: <ZR+YX6whnmZlnFv4@dread.disaster.area>


>>>>> @@ -690,17 +690,48 @@ _require_btrfs_scratch_logical_resolve_v2()
>>>>>        _scratch_unmount
>>>>>    }
>>>>>
>>>>> +post_scratch_mkfs_cmd()
>>>>> +{
>>>>> +    if [[ -v POST_SCRATCH_MKFS_CMD ]]; then
>>>>> +        echo "$POST_SCRATCH_MKFS_CMD $SCRATCH_DEV"
>>>>> +        $POST_SCRATCH_MKFS_CMD $SCRATCH_DEV
>>>>> +        return $?
>>>>> +    fi
> 
> Ideally this should be something like:
> 
> export SCRATCH_BTRFS_UUID='<uuid spec>'
> 
> btrfs_tune_dev() {
> 	local dev="$1"
> 
> 	if [ -n "$SCRATCH_BTRFS_UUID" ]; then
> 		btrfstune -m $SCRATCH_BTRFS_UUID $dev
> 		return $?
> 	fi
> 	return 0;
> }
> 
> _scratch_pool_mkfs_btrfs()
> {
> 	.....
> 	btrfs_tune_dev $SCRATCH_DEV_POOL
> 	.....
> }	
> 
> _scratch_mkfs_btrfs()
> {
> 	.....
> 	btrfs_tune_dev $SCRATCH_DEV
> 	.....
> }	
> 
> See how different it becomes when you stop thinking about filesystem
> configuration as a generic post-mkfs command and instead think of it
> as just another configuration option?


There's a possibility that mkfs.btrfs might include an option similar
to btrfstune -m, but its main purpose would likely be for running
fstests as there isn't any other use-case for it. If this addition
happens, I can withdraw this patch.

However, to clarify your approach mentioned above, if we want to set
SCRATCH_BTRFS_UUID to the UUID of TEST_DEV, then the config file
should contain something like this:

    SCRATCH_BTRFS_UUID=$(blkid /dev/sda1 | awk '{print $2}' | cut -d"=" 
-f2 | sed s/\"//g)


This should go in the config file. Right?

Thanks, Anand

  reply	other threads:[~2023-10-09 12:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28  4:23 [PATCH 0/2] fstests: add config option to run after mkfs Anand Jain
2023-09-28  4:23 ` [PATCH 1/2] fstests: btrfs streamlining mkfs command for post-mkfs operations Anand Jain
2023-09-28  4:23 ` [PATCH 2/2] fstests: add configuration option for executing post mkfs commands Anand Jain
2023-09-28  4:26   ` Qu Wenruo
2023-09-28  5:34     ` Anand Jain
2023-09-28  7:40       ` Qu Wenruo
2023-10-06  5:17         ` Dave Chinner
2023-10-09 12:18           ` Anand Jain [this message]
2023-10-06  6:09         ` Darrick J. Wong
2023-10-06  6:46           ` Qu Wenruo
2023-10-06 22:12             ` Dave Chinner
2023-10-07  2:45               ` Qu Wenruo
2023-10-09 12:23           ` 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=d4e7ba14-dc94-4611-8f7d-e3c5aafe80e1@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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).