On Dienstag, 28. Mai 2019 06:31:00 CEST Chris Murphy wrote: > On Mon, May 27, 2019 at 3:33 PM Dennis Schridde <devurandom@xxxxxxx> 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:
signature.asc
Description: This is a digitally signed message part.
