From: Zorro Lang <zlang@redhat.com>
To: Gabriel Niebler <gniebler@suse.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] README: Add tiny note concerning required scratch devs for btrfs testing
Date: Mon, 6 Feb 2023 22:52:07 +0800 [thread overview]
Message-ID: <20230206145207.kik5cczepdlgmexa@zlang-mailbox> (raw)
In-Reply-To: <20230131123839.16084-3-gniebler@suse.com>
On Tue, Jan 31, 2023 at 01:38:39PM +0100, Gabriel Niebler wrote:
> Signed-off-by: Gabriel Niebler <gniebler@suse.com>
> ---
> README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/README b/README
> index 008d3875..574cdd34 100644
> --- a/README
> +++ b/README
> @@ -127,7 +127,7 @@ Setup Environment
> - device contents will be destroyed.
>
> 4. (optional) Create SCRATCH device pool.
> - - needed for BTRFS testing
> + - needed for BTRFS testing (some tests require up to 5 disks of 10GB each)
Not sure about this part, so btrfs recommend 5 disks of 10GB each in
SCRATCH_DEV_POOL, to run all btrfs related tests? Does anyone know that?
Or can you provide the subcase names which need "5 disks of 10GB each",
to help to check and review?
P.S. I'm thinking about if this "(...)" should be moved to below item.
vvvvv
> - specifies 3 or more independent SCRATCH devices via the SCRATCH_DEV_POOL
> variable e.g SCRATCH_DEV_POOL="/dev/sda /dev/sdb /dev/sdc"
> - device contents will be destroyed.
> --
> 2.39.1
>
next prev parent reply other threads:[~2023-02-06 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 12:38 [PATCH 0/2] README: Add distro and btrfs testing info Gabriel Niebler
2023-01-31 12:38 ` [PATCH 1/2] README: Add section to install required packages on (open)SUSE Gabriel Niebler
2023-02-06 14:45 ` Zorro Lang
2023-01-31 12:38 ` [PATCH 2/2] README: Add tiny note concerning required scratch devs for btrfs testing Gabriel Niebler
2023-02-06 14:52 ` Zorro Lang [this message]
2023-02-06 16:29 ` Gabriel Niebler
2023-02-18 6:26 ` Zorro Lang
2023-02-22 17:24 ` Gabriel Niebler
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=20230206145207.kik5cczepdlgmexa@zlang-mailbox \
--to=zlang@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=gniebler@suse.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