From: "Chris Murphy" <lists@colorremedies.com>
To: "Mark Harmstone" <mark@harmstone.com>,
"Filipe Manana" <fdmanana@kernel.org>
Cc: "David Sterba" <dsterba@suse.cz>,
"David Sterba" <dsterba@suse.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs progs release 6.16.1
Date: Sun, 21 Sep 2025 14:25:34 -0400 [thread overview]
Message-ID: <a529e1bd-49c2-4463-90fe-847dd2c128f7@app.fastmail.com> (raw)
In-Reply-To: <eaf33285-5d77-4b7e-851a-61e40e61d3ae@harmstone.com>
I resolved it with a single command:
mount -o clear_cache,space-cache=v2 /dev/dm-1 /mnt
clear_cache alone doesn't resolve it because a subsequent mount creates a v1 cache by default (kernel 6.17.0-0.rc6.49.fc43.x86_64)
My question is if it makes sense for the kernel to be capable of, by default, fixing problems like this? Future feature?
For now though, the `btrfs check` message lacks an indication of the (un)seriousness of the problem, or what the user should do about it. Maybe this message could be prefaced with INFO: ? to suggest it's just an informational level concern?
The problem with the message and documentation is users are being advised to ask a btrfs developer or expert what to do about this message. So I kinda expect there will be messages on this list from users asking about it.
---
Chris Murphy
next prev parent reply other threads:[~2025-09-21 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 17:50 Btrfs progs release 6.16.1 David Sterba
2025-09-17 15:41 ` Filipe Manana
2025-09-18 0:33 ` David Sterba
2025-09-18 5:10 ` Mark Harmstone
2025-09-18 12:17 ` Filipe Manana
2025-09-18 13:05 ` Mark Harmstone
2025-09-21 18:25 ` Chris Murphy [this message]
2025-09-21 18:32 ` Chris Murphy
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=a529e1bd-49c2-4463-90fe-847dd2c128f7@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=mark@harmstone.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