From: Anand Jain <anand.jain@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org, zlang@redhat.com
Subject: Re: [PATCH v1] fstests: add configuration option for executing post mkfs commands
Date: Sun, 17 Sep 2023 19:58:11 +0800 [thread overview]
Message-ID: <87f9bf67-f407-e0b5-c29a-825eb4712392@oracle.com> (raw)
In-Reply-To: <ZQO6lmjasMPY8wOQ@dread.disaster.area>
> In general, we've put filesystem specific post-mkfs commands inside
> the filesystem specific mkfs function.
>
>
> See _scratch_mkfs_xfs() for example. If we want to test TB scale
> scratch filesystems without requiring ENOSPC tests to fill TBs of
> disk space, we set LARGE_SCRATCH_DEV. This causes the mkfs function
> to do the post-mkfs creation of a hidden file that consumes all but
> 50GB of space via fallocate (by calling _setup_large_xfs_fs()).
> Hence filesystem filling tests don't spend forever filling the
> filesystem, and no code outside of XFS specific functions need to
> care that this hidden file exists....
>
> Given that the use case here is to issue filesystem specific
> commands rather than generic setup commands needed for all
> filesystems, I think it would be better to encapsulate it inside the
> btrfs specific mkfs implementation....
>
IMO, making it configurable and generic would also benefit other
filesystems. For instance, the XFS filesystem could set it to
'POST_MKFS_CMD="xfs_admin -p"' or something similar ?
The design choice here is to create an open and configurable command
variable. This is because we have several commands and options that
we need to test, and it wouldn't be practical to hardcode them.
Any comments would be appreciated. I thought I would check again; I
don't mind hardcoding it to a command specific to btrfs only if
you still think it wouldn't be useful otherwise."
Thanks, Anand
next prev parent reply other threads:[~2023-09-17 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 9:04 [PATCH RFC] fstests: add configuration option for executing post mkfs commands Anand Jain
2023-09-14 15:07 ` [PATCH v1] " Anand Jain
2023-09-15 1:59 ` Dave Chinner
2023-09-17 11:58 ` Anand Jain [this message]
2023-09-18 1:18 ` Dave Chinner
2023-09-28 5:19 ` 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=87f9bf67-f407-e0b5-c29a-825eb4712392@oracle.com \
--to=anand.jain@oracle.com \
--cc=david@fromorbit.com \
--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;
as well as URLs for NNTP newsgroup(s).