From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Filipe Manana <fdmanana@kernel.org>,
Maxim Mikityanskiy <maxtram95@gmail.com>,
linux-btrfs@vger.kernel.org, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Qu Wenruo <wqu@suse.com>
Subject: Re: btrfs corruption, extent buffer leak
Date: Mon, 23 Jan 2023 14:35:57 +0100 [thread overview]
Message-ID: <20230123133557.GO11562@suse.cz> (raw)
In-Reply-To: <e08376e2-0722-b8b0-fe72-645a08972fcf@gmx.com>
On Mon, Jan 23, 2023 at 08:50:38PM +0800, Qu Wenruo wrote:
>
>
> On 2023/1/23 18:39, Filipe Manana wrote:
> > On Sat, Jan 21, 2023 at 1:59 PM Maxim Mikityanskiy <maxtram95@gmail.com> wrote:
> >>
> [...]
> >>
> >> Opening filesystem to check...
> >> Checking filesystem on /dev/mapper/root
> >> UUID: ********-****-****-****-************
> >> [1/7] checking root items
> >> [2/7] checking extents
> >> [3/7] checking free space tree
> >> [4/7] checking fs roots
> >> [5/7] checking only csums items (without verifying data)
> >> [6/7] checking root refs
> >> [7/7] checking quota groups
> >> ERROR: failed to add qgroup relation, member=258 parent=71776119061217538: No such file or directory
> >> ERROR: loading qgroups from disk: -2
> >> ERROR: failed to check quota groups
> >
> > This is a different issue, it's the first time I see it, nothing
> > related to the previous one. I'm adding Qu to CC since he knows
> > qgroups much better than I do, and so he may have an idea.
>
> This looks like that, we have a relation key, but there is no such qgroup.
>
> Not a big deal, you can disable qgroup, and re-enable qgroup.
> Which would rebuild the whole qgroup tree, although it means you lost
> the qgroup relationship, and need to re-add them.
We should have an easy way to dump and restore the relation tree and
limits. The 'qgroup show' command can now do the json output so it's a
bit easier to gnerate the list of commands to recreate the relations,
but such tool does not exist yet.
prev parent reply other threads:[~2023-01-23 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 13:29 btrfs corruption, extent buffer leak Maxim Mikityanskiy
2023-01-23 10:39 ` Filipe Manana
2023-01-23 12:03 ` Maxim Mikityanskiy
2023-01-23 13:23 ` Filipe Manana
2023-01-24 15:51 ` Maxim Mikityanskiy
2023-01-24 22:59 ` Qu Wenruo
2023-01-23 12:50 ` Qu Wenruo
2023-01-23 13:35 ` 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=20230123133557.GO11562@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=maxtram95@gmail.com \
--cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).