All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Schridde <devurandom@gmx.net>
To: "Szalma László" <dblaci@dblaci.hu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: parent transid verify failed on 604602368 wanted 840641 found 840639
Date: Tue, 28 May 2019 14:36:05 +0200	[thread overview]
Message-ID: <5695711.43npD3TUoY@monk> (raw)
In-Reply-To: <2a6df734-4c39-2f8a-7d8f-c627c2c15f76@dblaci.hu>

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

Dear Szalma!

Thank you for the information.

On Dienstag, 28. Mai 2019 08:40:40 CEST Szalma László wrote:
> I experienced the same, the problem is with bcache + gcc9. Immediately
> remove the cache device from the bcache, as it prevents more damages to
> your filesystem. After it downgrade gcc to 8 or avoid using bcache (with
> cache device) until the problem is solved by upstream.
>
> Please see here for more information:
> https://bugzilla.kernel.org/show_bug.cgi?id=203573
> 
> This is a very serious issue I think, but in my case I could save all my
> files after reboot without bcache cache device (except 1 insignificant
> one), but I guess you might need backups (I hope you have).

I did the following so far:

readlink /sys/fs/bcache/*/cache0/set | sed 's,.*/,,' > /sys/block/bcache0/
bcache/detach

How should I proceed from here on the path that you took to recover your 
system?

--Dennis

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2019-05-28 12:36 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
2019-05-28  6:40 ` Szalma László
2019-05-28 12:36   ` Dennis Schridde [this message]
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=5695711.43npD3TUoY@monk \
    --to=devurandom@gmx.net \
    --cc=dblaci@dblaci.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.