Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: do not use async discard for misc/004
Date: Wed, 12 Jun 2024 21:54:07 +0200	[thread overview]
Message-ID: <20240612195407.GP18508@twin.jikos.cz> (raw)
In-Reply-To: <5a292583be11ae383e79aaca0fa79be2141ef6ca.1717732459.git.wqu@suse.com>

On Fri, Jun 07, 2024 at 08:00:45PM +0930, Qu Wenruo wrote:
> [BUG]
> There is a long long existing failure in my local VM that with any newer
> kernel (6.x) the test case misc/004 would fail with ENOSPC during
> balance:
> 
>     [TEST]   misc-tests.sh
>     [TEST/misc]   004-shrink-fs
>  failed: /home/adam/btrfs-progs/btrfs balance start -mconvert=single -sconvert=single -f /home/adam/btrfs-progs/tests/mnt
>  test failed for case 004-shrink-fs
>  make: *** [Makefile:547: test-misc] Error 1
> 
> [CAUSE]
> With more testing, it turns out that just before the balance, the
> filesystem still have several empty data block groups.
> 
> The reason is the new default discard=async behavior, as it also changes
> the empty block groups to be async, this leave the empty block groups
> there, resulting no extra space for the convert balance.
> 
> [FIX]
> I do not understand why for loopback block devices we also enable
> discard, but at least disable discard for the test case so that we can
> ensure the empty block groups get cleaned up properly.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>

Added to devel, thanks.

      reply	other threads:[~2024-06-12 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 10:30 [PATCH] btrfs-progs: do not use async discard for misc/004 Qu Wenruo
2024-06-12 19:54 ` David Sterba [this message]

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=20240612195407.GP18508@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@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