From: Dennis Schridde <devurandom@gmx.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: parent transid verify failed on 604602368 wanted 840641 found 840639
Date: Tue, 28 May 2019 14:15:15 +0200 [thread overview]
Message-ID: <4832525.7q4I5aUDuF@monk> (raw)
In-Reply-To: <CAJCQCtRS1vvaczdpkYjkzWHWZgPxyq_B7XR9tY5yHhGAaBU7qA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]
On Dienstag, 28. Mai 2019 06:31:00 CEST Chris Murphy wrote:
> On Mon, May 27, 2019 at 3:33 PM Dennis Schridde <devurandom@gmx.net> wrote:
> > Yesterday I upgraded from Linux 5.1.1 (built with GCC 8.3.0) to Linux
> > 5.1.4
> > (built with GCC 9.1.0). The next boot was extremely slow and the desktop
> > environment (KDE Plasma) never really started, but got kind of stuck in
> > the
> > startup screen. So I switched to a VT and pressed ctrl+alt+del. The next
> > boot stopped early with following message:
> >
> > [T445] BTRFS: device label <...> devid 1 transid 840641 /dev/bcache0
> > [T599] BTRFS info (device bcache0): disk space caching is enabled
> > [T599] BTRFS info (device bcache0): has skinny extents
> > [T599] BTRFS error (device bcache0): parent transid verify failed on
> > 604602368 wanted 840641 found 840639
> > [T599] BTRFS error (device bcache0): open_ctree failed
> >
> > How can I recover from this?
> >
> > The filesystem should have several snapshots (created by snapper [1], on
> > every boot and hourly). Will they be of any help recovering my data?
> >
> > Best regards,
> > Dennis
> >
> > [1]: http://snapper.io/
>
> What happens if you revert to 5.1.1? That error suggests the super
> wants a newer transid than what exist on the filesystem, which
> suggests file system metadata was dropped. It's not certain from this
> information what caused that: device, or some layer in between like
> bcache, or Btrfs.
The basic issue appears to be the same with Linux 5.1.1:
[T512] BTRFS: device label <...> devid 1 transid 840641 /dev/bcache0
[T587] BTRFS info (device bcache0): disk space caching is enabled
[T587] BTRFS info (device bcache0): has skinny extents
[T587] BTRFS error (device bcache0): parent transid verify failed on 368672768
wanted 840529 found 840072
[T587] BTRFS error (device bcache0): failed to read block groups: -5
[T587] BTRFS error (device bcache0): open_ctree failed
I think on subsequent boots Linux 5.1.4 also pointed out other transids than
"wanted 840641 found 840639", but I am not sure and I am hesitant to keep
rebooting in case that means loosing more data.
--Dennis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2019-05-28 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 21:33 parent transid verify failed on 604602368 wanted 840641 found 840639 Dennis Schridde
2019-05-28 4:31 ` Chris Murphy
2019-05-28 12:15 ` Dennis Schridde [this message]
2019-05-28 6:40 ` Szalma László
2019-05-28 12:36 ` Dennis Schridde
2019-05-28 12:51 ` Szalma László
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=4832525.7q4I5aUDuF@monk \
--to=devurandom@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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