From: Boris Burkov <boris@bur.io>
To: Marc MERLIN <marc_btrfs@merlins.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Josef Bacik <josef@toxicpanda.com>, QuWenruo <wqu@suse.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
Filipe Manana <fdmanana@kernel.org>,
Chris Murphy <lists@colorremedies.com>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
Roman Mamedov <rm@romanrm.net>, To: Su Yue <Damenly_Su@gmx.com>,
Su Yue <suy.fnst@cn.fujitsu.com>;
Subject: Re: Simple quota unsafe? RIP: 0010:__btrfs_free_extent.isra.0+0xc41/0x1020 [btrfs] / do_free_extent_accounting:2999: errno=-2 No such entry
Date: Wed, 15 Apr 2026 10:05:10 -0700 [thread overview]
Message-ID: <20260415170510.GA780391@zen.localdomain> (raw)
In-Reply-To: <ad8gcwTFOLUhBHGA@merlins.org>
On Tue, Apr 14, 2026 at 10:21:55PM -0700, Marc MERLIN wrote:
> If you don't mind my asking, and even if it's just a guess:
>
> 1) do you feel squotas are likely safe and I hit another bug?
I actually think it is a squota bug and am trying to reproduce it. I
think there may be a gap if we are deleting the qgroup in the same
transaction as the last delayed ref in the qgroup.
In meta production I have a carryover patch ignoring such enoents, which
makes me super suspicious.
I have not reproduced it yet, though.
The fact that the two stacks are in balance and qgroup deletion make me
suspicious. On the other hand, the fact that the second stack is in the
commit *before* the majority of the cleanup makes me less
suspicious.
> 2) any chance it can be block-group-tree instead? Are those
> considered reasonably safe? (I enabled due to the number of
> snapshots, 100+, and being told it's bad for perf to have that
> many, which block-group-tree is supposed to fix)
I think that is relatively unlikely.
> 3) anyone still taking bugs for btrfs check --repair since it
> fixed nothing on an unmountable filesystem
If my suspicion is correct and this does end up being a missing qgroup I
think that I could likely have a useful fix for check --repair too.
> 4) anything useful to anyone in my broken filesystem which might
> be easy to fix but not by me before I give up, delete it all
> and do the multi week restore?
I think trying to dump the state of the tree on your laptop could be
quite useful.
1258303029248 is the logical address we were freeing so its backrefs in
the extent tree will be interesting. As will whatever subvol tree it is
in, as will the qgroup tree entry for that subvolid. If you can share a
full dump then I can find all that myself.
ditto for the logical address that broke on the rpi, but if that is a
gigantic fs, maybe doing the dump will be pretty unwieldy..
Thanks for your help with this,
Boris
>
> Thanks,
> Marc
> --
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
>
> Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
next prev parent reply other threads:[~2026-04-15 17:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 3:35 BTRFS discard crash: failed to run delayed ref for logical 15506102321152 num_bytes 16384 type 182 action 2 ref_mod 1: -2 6.11.2) Marc MERLIN
2026-04-11 4:47 ` Qu Wenruo
2026-04-11 12:04 ` Roman Mamedov
2026-04-11 16:22 ` Marc MERLIN
2026-04-12 1:57 ` Marc MERLIN
2026-04-12 1:57 ` Marc MERLIN
2026-04-12 2:28 ` Marc MERLIN
2026-04-12 2:28 ` Marc MERLIN
2026-04-12 17:38 ` Marc MERLIN
2026-04-12 17:38 ` Marc MERLIN
2026-04-12 20:21 ` Marc MERLIN
2026-04-12 20:21 ` Marc MERLIN
2026-04-13 2:14 ` Roman Mamedov
2026-04-13 2:34 ` Marc MERLIN
2026-04-13 2:34 ` Marc MERLIN
2026-04-13 17:52 ` Simple quota unsafe? RIP: 0010:__btrfs_free_extent.isra.0+0xc41/0x1020 [btrfs] / do_free_extent_accounting:2999: errno=-2 No such entry Marc MERLIN
2026-04-13 17:52 ` Marc MERLIN
2026-04-13 18:47 ` Boris Burkov
2026-04-13 19:40 ` Marc MERLIN
2026-04-13 19:40 ` Marc MERLIN
2026-04-15 5:21 ` Marc MERLIN
2026-04-15 17:05 ` Boris Burkov [this message]
2026-04-15 17:59 ` Marc MERLIN
2026-04-15 18:44 ` Boris Burkov
2026-04-15 20:22 ` Marc MERLIN
2026-04-15 22:36 ` Boris Burkov
2026-04-15 22:55 ` Marc MERLIN
2026-04-15 23:25 ` Boris Burkov
2026-04-16 0:55 ` Marc MERLIN
2026-04-16 1:22 ` Boris Burkov
2026-04-16 0:45 ` Boris Burkov
2026-04-16 1:08 ` Marc MERLIN
2026-04-16 1:25 ` Boris Burkov
2026-04-16 16:51 ` Simple quota unsafe (FIXED: btrfstune --remove-simple-quota worked) Marc MERLIN
2026-04-16 17:21 ` Simple quota unsafe? RIP: 0010:__btrfs_free_extent.isra.0+0xc41/0x1020 [btrfs] / do_free_extent_accounting:2999: errno=-2 No such entry Marc MERLIN
2026-04-16 21:36 ` Boris Burkov
2026-04-16 21:47 ` Marc MERLIN
2026-04-17 21:51 ` Boris Burkov
2026-04-17 22:37 ` Marc MERLIN
2026-04-17 23:16 ` Boris Burkov
2026-04-18 0:18 ` Marc MERLIN
2026-04-17 3:43 ` BTRFS discard crash: failed to run delayed ref for logical 15506102321152 num_bytes 16384 type 182 action 2 ref_mod 1: -2 6.11.2) David Disseldorp
2026-04-17 5:19 ` Marc MERLIN
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=20260415170510.GA780391@zen.localdomain \
--to=boris@bur.io \
--cc=Damenly_Su@gmx.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=marc_btrfs@merlins.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=rm@romanrm.net \
--cc=suy.fnst@cn.fujitsu.com \
--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