All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [BUG] BTRFS critical corrupt leaf - bisected to 496245cac57e
Date: Tue, 30 Jul 2019 22:16:46 +0800	[thread overview]
Message-ID: <afa404af-1365-9763-b0e7-7a5a088f4d49@gmx.com> (raw)
In-Reply-To: <bc23aa4a-2240-80d6-c2c2-d060191f884b@petaramesh.org>



On 2019/7/30 下午9:57, Swâmi Petaramesh wrote:
> Hello,
>
> Le 30/07/2019 à 09:21, Qu Wenruo a écrit :
>> Unfortunately, transid error here helps nothing.
>
> Now, each and everytime I try to mount this disk on the original
> machine, or another one, I get :

When the message shows, it means the damage is already done *BEFORE*.

Really nothing to do with your current kernel version.

If it's the fault of btrfs or device mapper, then it's related to the
kernel used in last unmount (if unmounted cleanly) or last unclean
shutdown before hitting this error.

If it's the hardware, you'd check if your disk has unreliable flush/fua
behavior, then different kernel may have some difference in how it's
affected, but nothing can save you.

>
> systemd[1]: run-media-xxxxxxxxxxxxxxxx.mount: Succeeded.
> kernel: BTRFS info (device dm-2): disk space caching is enabled
> kernel: BTRFS info (device dm-2): has skinny extents
> kernel: BTRFS error (device dm-2): parent transid verify failed on
> 2137144377344 wanted 7684 found 7499
> kernel: BTRFS error (device dm-2): parent transid verify failed on
> 2137144377344 wanted 7684 found 7499
> kernel: BTRFS error (device dm-2): parent transid verify failed on
> 2137144377344 wanted 7684 found 7499
> kernel: BTRFS: error (device dm-2) in btrfs_drop_snapshot:9465: errno=-5
> IO failure
> kernel: BTRFS info (device dm-2): forced readonly
>
> (It first appears to mount OK, then the errors follow a few seconds
> afterwards, and the it remounts readonly).
>
> The "7499" displays seems to correspond to the most recent snapshot
> created on the disk (using btrfs su li).
>
> Is there any way I could repair this several-TB FS, ever if it implies
> losing the latest (or a few of the latest) created subvols and snapshots ?

Short answer: no.

If you want to recover to a rw mountable fs and pass btrfs check, the
chance is very low, as the corruption happens in extent tree, an
essential tree to write operations.
Corruption there is not easy to repair to pass btrfs check again.

Thanks,
Qu

>
> TIA.
>
> Kind regards.
>

      reply	other threads:[~2019-07-30 14:16 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
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 [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=afa404af-1365-9763-b0e7-7a5a088f4d49@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --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 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.