FS/XFS testing framework
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Neal Gompa <neal@gompa.dev>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs: remove test case btrfs/131
Date: Mon, 1 Jan 2024 08:44:25 +1030	[thread overview]
Message-ID: <cea1fa09-df9c-4234-9b00-941d07afb706@suse.com> (raw)
In-Reply-To: <CAEg-Je9vT-VwVtkqj2pszP08kmk9npPkf-OsSwe3G93m0YsxXw@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1361 bytes --]



On 2024/1/1 00:42, Neal Gompa wrote:
> On Sat, Dec 30, 2023 at 6:37 PM Qu Wenruo <wqu@suse.com> wrote:
>>
>> Test case btrfs/131 is a quick tests for v1/v2 free space related
>> behavior, including the mount time conversion and disabling of v2 space
>> cache.
>>
>> However there are two problems, mostly related to the v2 cache clearing.
>>
>> - There are some features with hard dependency on v2 free space cache
>>    Including:
>>    * block-group-tree
>>    * extent-tree-v2
>>    * subpage support
>>
>>    Note those features may even not support clearing v2 cache.
>>
>> - The v1 free space cache is going to be deprecated
>>    Since v5.15 the default mkfs is already going v2 cache instead.
>>    It won't be long before we mark v1 cache deprecated and force to
>>    go v2 cache.
>>
>> This makes the test case to fail unnecessarily, the false failure would
>> only grow with new features relying on v2 cache.
>>
>> So here let's removing the test case completely.
>>
> 
> Can we pair this change with a corresponding change in btrfs-progs
> that blocks using v1? I don't think it's actually worth splitting this
> change up in phases, especially when we're explicitly dropping the
> tests around it.

That sounds pretty reasonable.

I'll craft one to deprecate v1 cache in progs too.

Thanks,
Qu
> 
> 

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7027 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2023-12-31 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 23:36 [PATCH] fstests: btrfs: remove test case btrfs/131 Qu Wenruo
2023-12-31 14:12 ` Neal Gompa
2023-12-31 22:14   ` Qu Wenruo [this message]
2024-01-01  0:00     ` Neal Gompa

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=cea1fa09-df9c-4234-9b00-941d07afb706@suse.com \
    --to=wqu@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=neal@gompa.dev \
    /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