From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: Correct way to clear a free space cache file invalid error
Date: Mon, 16 Jan 2023 11:22:23 +0100 [thread overview]
Message-ID: <2269684.ElGaqSPkdT@lichtvoll.de> (raw)
Sorry for incomplete subject, reposting.
Hi!
Kernel 6.1, btrfs-progs 6.1.2. Filesystem on NVME SSD, via LVM and dm-
crypt.
I would like
[ 18.657903] BTRFS info (device dm-1): the free space cache file
(23912775680) is invalid, skip it
[ 18.697033] BTRFS info (device dm-1): the free space cache file
(25254952960) is invalid, skip it
to be gone.
So I tried
mount -o remount,clear_cache,space_cache=v1 /
as well as
mount -o remount,clear_cache /
mount -o remount,space_cache=v1 /
to no avail.
Before that I had space cache v2 on the filesystem as with most of my
other BTRFS filesystems. But since it really should not be necessary for
a 50 GiB filesystem for the Linux system (not user data), I thought I
play it safe this time. At least from what I learned from btrfs manpage.
In a page on BTRFS wiki it is stated that one should run "btrfs check"
on the filesystem.
So what is the correct way to clear that error?
I did not perceive any malfunctioning due to the error in dmesg. The
filesystem scrubs without errors.
Best,
--
Martin
next reply other threads:[~2023-01-16 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 10:22 Martin Steigerwald [this message]
2023-01-16 10:41 ` Correct way to clear a free space cache file invalid error Qu Wenruo
2023-01-16 14:07 ` [PATCH] btrfs-progs: docs: improve space cache documentation Christoph Anton Mitterer
2023-01-16 15:24 ` Christoph Anton Mitterer
2023-01-16 15:30 ` Correct way to clear a free space cache file invalid error Martin Steigerwald
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=2269684.ElGaqSPkdT@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.