All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Niebler <gniebler@suse.com>
To: Zorro Lang <zlang@redhat.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 17:29:14 +0100	[thread overview]
Message-ID: <f8d78191-089f-4407-dd2d-17f7e3be2580@suse.com> (raw)
In-Reply-To: <20230206145207.kik5cczepdlgmexa@zlang-mailbox>

Am 06.02.23 um 15:52 schrieb Zorro Lang:
> 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?

Of course (and thanks for asking, as it turns out my recollection was 
slightly wrong on that one):

To begin with, btrfs/011[1] states the "5 disks" requirement in the 
lengthy comment at the top of the file:
"""
# The amount of tests done depends on the number of devices in the
# SCRATCH_DEV_POOL. For full test coverage, at least 5 devices should
# be available (e.g. 5 partitions).
""
... but it doesn't say anything about device size.

btrfs/027[2] however checks the presence of 5 devices in 
$SCRATCH_DEV_POOL directly in code and also runs a check to ensure that 
all of these devices are *of the same size*.

And then there are at least two tests that require $SCRATCH_DEV to be 
10GB or more in size:
- btrfs/079[3], which writes a 10G file to $SCRATCH_MNT and
- btrfs/253[4], which directly creates a 10G FS on $SCRATCH_DEV.

*Taken together*, this means that for full btrfs test coverage, one 
needs a $SCRATCH_DEV_POOL with at least 5 devices of equal size in it 
and that size has to be at least 10GB.

But that makes the remark wrong, strictly speaking, as there's no single 
test that requires "at least 5 devices of 10GB each".

How about this: "(for full btrfs test coverage, use at least 5 devices 
of equal size and at least 10GB)"

> 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"

Fine by me! :-)

[1]: 
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/tests/btrfs/011#n10
[2]: 
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/tests/btrfs/027#n20
[3]: 
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/tests/btrfs/079#n44
[4]: 
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/tests/btrfs/253#n90

  reply	other threads:[~2023-02-06 16:29 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
2023-02-06 16:29     ` Gabriel Niebler [this message]
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=f8d78191-089f-4407-dd2d-17f7e3be2580@suse.com \
    --to=gniebler@suse.com \
    --cc=fstests@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.