All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, alexander.wetzel@web.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [BUG] BTRFS critical corrupt leaf - bisected to 496245cac57e
Date: Tue, 30 Jul 2019 08:44:59 +0200	[thread overview]
Message-ID: <508c6378-522a-ae24-6c33-83c8efc64ae5@petaramesh.org> (raw)
In-Reply-To: <4776e0bd-83c2-44a1-4403-3a155fe3f6c7@gmx.com>

Le 30/07/2019 à 06:56, Qu Wenruo a écrit :
>>>
>>> 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
> 
> Ping? If you really want to solve the problem, please provide the full
> kernel message.

Hi,

I have emergency downgraded my system to 5.1 not to take any risk of
crashing my SSD again (and if it crashes again anyway, then I will know
it is not kernel 5.2's fault and let you know...)

I don't have the « first kernel messages » for the SSD because I
restored it to a backup before it failed, so obviously last kernel
messages were lost.

This morning if I try to scrub (using kernel5.1.16-arch1-1-ARCH) the
external HD that failed yesterday, I get :

BTRFS info (device dm-3): scrub: started on devid 1
BTRFS error (device dm-3): parent transid verify failed on 2137144377344
wanted 7684 found 7499
BTRFS error (device dm-3): parent transid verify failed on 2137144377344
wanted 7684 found 7499
BTRFS error (device dm-3): parent transid verify failed on 2137144377344
wanted 7684 found 7499
BTRFS: error (device dm-3) in btrfs_drop_snapshot:9603: errno=-5 IO failure
BTRFS info (device dm-3): forced readonly
BTRFS warning (device dm-3): failed setting block group ro: -30
BTRFS info (device dm-3): scrub: not finished on devid 1 with status: -30

Hope this helps...

ॐ

-- 
Swâmi Petaramesh <swami@petaramesh.org> PGP 9076E32E

  reply	other threads:[~2019-07-30  6:45 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
2019-07-30  4:56     ` Qu Wenruo
2019-07-30  6:44       ` Swâmi Petaramesh [this message]
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=508c6378-522a-ae24-6c33-83c8efc64ae5@petaramesh.org \
    --to=swami@petaramesh.org \
    --cc=alexander.wetzel@web.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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 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.