All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	fstests@vger.kernel.org,  linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/3] xfs/65[56]: don't unset SCRATCH_RTDEV here
Date: Mon, 20 Jul 2026 03:31:47 +0800	[thread overview]
Message-ID: <al0mCn2FhFGuiCGa@zlang-mailbox> (raw)
In-Reply-To: <20260710052747.1841555-3-hch@lst.de>

On Fri, Jul 10, 2026 at 07:27:34AM +0200, Christoph Hellwig wrote:
> From: "Darrick J. Wong" <djwong@kernel.org>
> 
> Both of these tests claim that they have to unset SCRATCH_RTDEV to avoid
> formatting failures due to the rt bitmap consuming all the space in the
> "small" data device.  However, the format doesn't constrain the size of
> the data device, so the justification doesn't apply.  Remove the whole
> thing.
> 
> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---

Reviewed-by: Zorro Lang <zlang@kernel.org>

>  tests/xfs/655 | 4 ----
>  tests/xfs/656 | 4 ----
>  2 files changed, 8 deletions(-)
> 
> diff --git a/tests/xfs/655 b/tests/xfs/655
> index a4162d70b321..9d09cc000531 100755
> --- a/tests/xfs/655
> +++ b/tests/xfs/655
> @@ -24,10 +24,6 @@ _require_scratch_nocheck
>  _require_scratch_xfs_crc # can't detect minor corruption w/o crc
>  _require_xfs_io_command healthmon
>  
> -# Disable the scratch rt device to avoid test failures relating to the rt
> -# bitmap consuming all the free space in our small data device.
> -unset SCRATCH_RTDEV
> -
>  echo "Format and mount"
>  _scratch_mkfs -d agcount=1 | _filter_mkfs 2> $tmp.mkfs >> $seqres.full
>  . $tmp.mkfs
> diff --git a/tests/xfs/656 b/tests/xfs/656
> index c01276eb384b..5114a6c24003 100755
> --- a/tests/xfs/656
> +++ b/tests/xfs/656
> @@ -40,10 +40,6 @@ filter_healer_errors() {
>  		uniq
>  }
>  
> -# Disable the scratch rt device to avoid test failures relating to the rt
> -# bitmap consuming all the free space in our small data device.
> -unset SCRATCH_RTDEV
> -
>  echo "Format and mount"
>  _scratch_mkfs > $seqres.full 2>&1
>  _dmerror_init no_log
> -- 
> 2.53.0
> 

  reply	other threads:[~2026-07-19 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  5:27 scratch rtdev handling improvements Christoph Hellwig
2026-07-10  5:27 ` [PATCH 1/3] xfs/656: rearrange directio pread/pwrite for zoned filesystems Christoph Hellwig
2026-07-19 19:31   ` Zorro Lang
2026-07-10  5:27 ` [PATCH 2/3] xfs/65[56]: don't unset SCRATCH_RTDEV here Christoph Hellwig
2026-07-19 19:31   ` Zorro Lang [this message]
2026-07-10  5:27 ` [PATCH 3/3] formalize and fix disabling the RT subvolume Christoph Hellwig
2026-07-10  6:10   ` Darrick J. Wong

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=al0mCn2FhFGuiCGa@zlang-mailbox \
    --to=zlang@kernel.org \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    /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.