From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: telsch <telsch@gmx.de>, linux-btrfs@vger.kernel.org
Subject: Re: tree-checker read time corruption
Date: Thu, 13 Feb 2020 15:14:59 +0100 [thread overview]
Message-ID: <02ee0b77-d04f-4fa0-e750-cfbe598f2cfa@applied-asynchrony.com> (raw)
In-Reply-To: <d250e7c2-76d4-1369-e440-c72370035842@gmx.de>
On 2/13/20 3:02 PM, telsch wrote:
>> According to the repair log, btrfs-progs doesn't detect it at all.
>> Thus I'm not sure if it's a bug in btrfs-progs or it's just not newer
>> enough.
>>
>> Anyway, you can delete inode 265 manually using older kernel.
>>
>> Thanks,
>> Qu
>
> Thanks for support. Deleting inode 265 manually fixed this mount issue
> with kernel >= 5.2 for me.
Btw the patches to fix up invalid generations that Qu referred to are
in btrfs-progs-5.4.*1*, not 5.4.
-h
prev parent reply other threads:[~2020-02-13 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 14:17 tree-checker read time corruption telsch
2020-02-12 0:41 ` Qu Wenruo
2020-02-12 14:20 ` telsch
2020-02-13 0:24 ` Qu Wenruo
2020-02-13 14:02 ` telsch
2020-02-13 14:14 ` Holger Hoffstätte [this message]
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=02ee0b77-d04f-4fa0-e750-cfbe598f2cfa@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=telsch@gmx.de \
/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).