From: Christoph Anton Mitterer <calestyo@scientia.org>
To: Tobias Powalowski <tobias.powalowski@googlemail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: 6.0.3 broke space_cache=v1 devices
Date: Sun, 23 Oct 2022 19:26:22 +0200 [thread overview]
Message-ID: <1c531dd5de7477c8b6ec15d4aebb8e42ae460925.camel@scientia.org> (raw)
In-Reply-To: <CAHfPjO-gtcdvzgjm1o5NdS0bRy8ukyROH24UhWUATn6ouj07yw@mail.gmail.com>
Hey.
At least the:
__btrfs_remove_free_space_cache
also shows up in my call traces:
https://lore.kernel.org/linux-btrfs/2291416ef48d98059f9fdc5d865b0ff040148237.camel@scientia.org/T/#u
Though I had the issue only on mv (and once on send|receive)...
otherwise my 6.0.3 v1-space-cache fs seem to work find (or maybe they
just pile up corruptions under the hood ^^).
Cheers,
Chris.
prev parent reply other threads:[~2022-10-23 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 17:19 6.0.3 broke space_cache=v1 devices Tobias Powalowski
2022-10-23 17:26 ` Christoph Anton Mitterer [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=1c531dd5de7477c8b6ec15d4aebb8e42ae460925.camel@scientia.org \
--to=calestyo@scientia.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=tobias.powalowski@googlemail.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).