From: Eric Levy <contact@ericlevy.name>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: parent transid verify failed
Date: Thu, 30 Dec 2021 16:10:23 -0500 [thread overview]
Message-ID: <c0c6ec8de80b8e10185fe1980377dcc7af8d3200.camel@ericlevy.name> (raw)
Hello.
I had a simple Btrfs partition, with only one subvolume, about 250 Gb
in size. As it began to fill, I added a second volume, live. By the
time the size of the file system reached the limit for the first
volume, the file system reverted to read only.
From journalctl, the following message has recurred, with the same
numeric values:
BTRFS error (device sdc1): parent transid verify failed on 867434496
wanted 9212 found 8675
Presently, the file system mounts only as read only. It will not mount
in read-write, even with the usebackuproot option.
It seems that balance and scrub are not available, either due to read-
only mode, or some other reason. Both abort as soon as they begin to
run.
What is the best next step for recovery?
next reply other threads:[~2021-12-30 21:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 21:10 Eric Levy [this message]
2021-12-30 21:47 ` parent transid verify failed Chris Murphy
2022-01-01 15:11 ` devel
2021-12-31 19:14 ` Zygo Blaxell
2021-12-31 20:33 ` Eric Levy
2021-12-31 23:09 ` Chris Murphy
2022-01-01 7:33 ` Eric Levy
2022-01-01 20:49 ` Chris Murphy
2022-01-01 21:57 ` Eric Levy
2022-01-01 20:56 ` Zygo Blaxell
2022-01-01 21:58 ` Eric Levy
2022-01-02 0:15 ` Zygo Blaxell
2022-01-02 0:55 ` Eric Levy
2022-01-02 3:27 ` Zygo Blaxell
2022-01-02 4:03 ` Eric Levy
2022-01-02 5:57 ` Zygo Blaxell
2022-01-02 10:17 ` Eric Levy
2022-01-03 7:41 ` Chris Murphy
2022-01-02 7:31 ` Andrei Borzenkov
-- strict thread matches above, loose matches on Subject: below --
2017-05-11 10:01 Massimo B.
[not found] <E18363B1-CD81-41F4-A03C-4D09AA669915@plack.net>
2015-04-28 12:34 ` Anthony Plack
2010-09-06 17:28 Jan Steffens
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=c0c6ec8de80b8e10185fe1980377dcc7af8d3200.camel@ericlevy.name \
--to=contact@ericlevy.name \
--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 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).