Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: "Stéphane Lesimple" <stephane_btrfs2@lesimple.fr>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: relocation: fix wrong file extent type check to avoid false -ENOENT error
Date: Wed, 6 Jan 2021 17:34:29 +0100	[thread overview]
Message-ID: <20210106163429.GU6430@twin.jikos.cz> (raw)
In-Reply-To: <7f932027eebe43b2e63908f1d4889e24@lesimple.fr>

On Tue, Jan 05, 2021 at 06:24:24PM +0000, Stéphane Lesimple wrote:
> FWIW, just recompiled with the patch to be 100% sure, as I still had
> the problematic FS around untouched:
> 
> [  199.722122] BTRFS info (device dm-10): balance: start -dvrange=34625344765952..34625344765953
> [  199.730267] BTRFS info (device dm-10): relocating block group 34625344765952 flags data|raid1
> [  212.232222] BTRFS info (device dm-10): found 167 extents, stage: move data extents
> [  236.124541] BTRFS info (device dm-10): found 167 extents, stage: update data pointers
> [  248.011778] BTRFS info (device dm-10): balance: ended with status: 0
> 
> As expected, all is good now!
> 
> Tested-By: Stéphane Lesimple <stephane_btrfs2@lesimple.fr>

Thanks for testing, tag added to the patch.

      reply	other threads:[~2021-01-06 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 13:29 [PATCH] btrfs: relocation: fix wrong file extent type check to avoid false -ENOENT error Qu Wenruo
2020-12-30  7:57 ` Su Yue
2021-01-04 16:16 ` David Sterba
2021-01-05 18:24   ` Stéphane Lesimple
2021-01-06 16:34     ` 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=20210106163429.GU6430@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stephane_btrfs2@lesimple.fr \
    --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