Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>, alexander.wetzel@web.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [BUG] BTRFS critical corrupt leaf - bisected to 496245cac57e
Date: Mon, 29 Jul 2019 21:33:39 +0800	[thread overview]
Message-ID: <d9ea9623-657e-0315-7166-b7f58b32d4e0@gmx.com> (raw)
In-Reply-To: <daeb4767-b113-f945-da67-61d250fa1663@petaramesh.org>



On 2019/7/29 下午8:46, Swâmi Petaramesh wrote:
> Hi,
>
> The corruption issue that you report just after upgrading to kernel 5.2
> resembles very much to what I had on 2 filesystems after such an upgrade.
>
> I think I'me gonna emergency downgrade all my BTRFS machines to kernel
> 5.1 before they break ,-(

Full kernel message please.

That commit is designed to corrupted inode item, we need more info to
determine if it's a real corruption or not.

Thanks,
Qu

>
>
> ॐ
>

  reply	other threads:[~2019-07-29 13:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13 20:48 [BUG] BTRFS critical corrupt leaf - bisected to 496245cac57e Alexander Wetzel
2019-07-14  1:30 ` Qu Wenruo
2019-07-14  9:25   ` Alexander Wetzel
2019-07-14  9:49     ` Qu Wenruo
2019-07-14 12:07       ` Alexander Wetzel
2019-07-14 12:51         ` Qu Wenruo
2019-07-14 15:40       ` Chris Murphy
2019-07-15  1:07         ` Qu Wenruo
2019-07-29 12:46 ` Swâmi Petaramesh
2019-07-29 13:33   ` Qu Wenruo [this message]
2019-07-30  4:56     ` Qu Wenruo
2019-07-30  6:44       ` Swâmi Petaramesh
2019-07-30  7:21         ` Qu Wenruo
2019-07-30  8:02           ` Swâmi Petaramesh
2019-07-30 13:57           ` Swâmi Petaramesh
2019-07-30 14:16             ` Qu Wenruo

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=d9ea9623-657e-0315-7166-b7f58b32d4e0@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=alexander.wetzel@web.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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