From: Remi Gauvin <remi@georgianit.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS corruption, mounts but comes read-only
Date: Sat, 5 Oct 2019 13:14:14 -0400 [thread overview]
Message-ID: <e546074f-4292-32c5-fe6b-170ace2f63f7@georgianit.com> (raw)
In-Reply-To: <8d765abc-b9f6-066f-8327-bcfc9a156177@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 857 bytes --]
On 2019-09-30 9:53 p.m., Qu Wenruo wrote:
>
> It's indeed a symptom of btrfs kernel module bug. But at least looks
> repairable.
>
As advertised, btrfs --check repair restored the FS to full function.
A follow-up scrub even found and corrected some corrupt data on one of
the disks, that went completely unreported by the disk itself. So,
despite this hiccup, BTRFS did it's job admirably.
Whenever I do any further btrfs check after cleanly unmounting the
filesystem, I get this error:
cache and super generation don't match, space cache will be invalidated
Even mounting with clear_cache,nospace_cache , (then mounting again with
space_cache=v2) does not remove this warning. But it doesn't seem to be
causing any problems.. There are no warnings about the space cache in
the dmesg log when the filesystem is mounted.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2019-10-05 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 19:57 BTRFS corruption, mounts but comes read-only Remi Gauvin
2019-09-30 21:08 ` Remi Gauvin
2019-10-01 1:30 ` Qu Wenruo
2019-10-01 1:41 ` Remi Gauvin
2019-10-01 1:53 ` Qu Wenruo
2019-10-05 17:14 ` Remi Gauvin [this message]
2019-10-05 23:18 ` Qu Wenruo
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=e546074f-4292-32c5-fe6b-170ace2f63f7@georgianit.com \
--to=remi@georgianit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).