FS/XFS testing framework
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, fstests@vger.kernel.org
Cc: josef@toxicpanda.com
Subject: Re: [PATCH 2/6] generic/352: require no compression
Date: Tue, 21 May 2024 08:04:37 +0800	[thread overview]
Message-ID: <47c223a3-0dd5-4e10-8697-54245f26ccb6@oracle.com> (raw)
In-Reply-To: <d3e67b7d53f21d3e290384760ffbfda02c43cc8c.1715896529.git.dsterba@suse.com>

On 5/17/24 06:12, David Sterba wrote:
> From: Josef Bacik <josef@toxicpanda.com>
> 
> Our CI has been failing on this test for compression since 0fc226e7
> ("fstests: generic/352 should accomodate other pwrite behaviors").  This
> is because we changed the size of the initial write down to 4k, and we
> write a repeatable pattern.  With compression on btrfs this results in
> an inline extent, and when you reflink an inline extent this just turns
> it into full on copies instead of a reflink.
> 
> As this isn't a bug with compression, it's just not well aligned with
> how compression interacts with the allocation of space, simply exclude
> this test from running when you have compression enabled.
> 
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---




>   tests/generic/352 | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/tests/generic/352 b/tests/generic/352
> index acc17dac38d061..3a18f07601de96 100755
> --- a/tests/generic/352
> +++ b/tests/generic/352
> @@ -25,6 +25,10 @@ _supported_fs generic
>   _require_scratch_reflink
>   _require_xfs_io_command "fiemap"
>   
> +# The size is too small, this will result in an inline extent and then reflink
> +# will simply be a copy on btrfs, so exclude compression.
> + _require_no_compress
> +


Reviewed-by: Anand Jain <anand.jain@oracle.com>

Thanks, Anand
>   _scratch_mkfs > /dev/null 2>&1
>   _scratch_mount
>   


  reply	other threads:[~2024-05-21  0:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 22:12 [PATCH 0/6] Btrfs test updates and fixups David Sterba
2024-05-16 22:12 ` [PATCH 1/6] common: udev settle before _scratch_pool_mkfs David Sterba
2024-05-17 21:57   ` Anand Jain
2024-05-20 19:21     ` David Sterba
2024-05-20 23:48       ` Anand Jain
2024-05-16 22:12 ` [PATCH 2/6] generic/352: require no compression David Sterba
2024-05-21  0:04   ` Anand Jain [this message]
2024-05-16 22:12 ` [PATCH 3/6] generic/027: " David Sterba
2024-05-21  0:09   ` Anand Jain
2024-05-16 22:12 ` [PATCH 4/6] generic/269: " David Sterba
2024-05-21  0:37   ` Anand Jain
2024-05-21 18:29     ` David Sterba
2024-05-16 22:12 ` [PATCH 5/6] btrfs/011: mkfs the scratch dev before exiting David Sterba
2024-05-17 15:37   ` Darrick J. Wong
2024-05-20 19:18     ` David Sterba
2024-05-16 22:12 ` [PATCH 6/6] btrfs/{140,141}: verify read-repair test data by md5sum David Sterba
2024-05-23 15:31   ` Anand Jain
2024-05-23 15:35 ` [PATCH 0/6] Btrfs test updates and fixups 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=47c223a3-0dd5-4e10-8697-54245f26ccb6@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=josef@toxicpanda.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