public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Tavian Barnes <tavianator@tavianator.com>, linux-btrfs@vger.kernel.org
Subject: Re: Corruption while bisecting (was: [PATCH] btrfs: tree-checker: dump the page status if hit something wrong)
Date: Mon, 26 Feb 2024 19:00:00 +1030	[thread overview]
Message-ID: <f9296554-9c90-4991-a67e-d1a8defafca3@gmx.com> (raw)
In-Reply-To: <CABg4E-=u7m_g3HCFUYHS-+RC==pefkUZXiTT2Aor86jruHSF9Q@mail.gmail.com>



在 2024/2/26 06:00, Tavian Barnes 写道:
> Well, bad news: I started bisecting from v6.0 and after a couple
> rounds, my root fs is really corrupted:
>
> UUID:             e1902620-c206-4e34-9f24-e66cdb6b8872
> Scrub started:    Sun Feb 25 18:47:29 2024
> Status:           finished
> Duration:         0:20:18
> Total to scrub:   2.72TiB
> Rate:             2.29GiB/s
> Error summary:    csum=2073625
>    Corrected:      0
>    Uncorrectable:  2073625
>    Unverified:     0
>
> All the errors seem confined to one of the four disks which is strange:

Mind to share which commit you're at when hitting the scrub errors?

And have you tried with offline scrub (aka, "btrfs check
--check-data-csum")?

IIRC during the rework of scrub, there are several regression caused by
the rework (e02ee89baa66 ("btrfs: scrub: switch scrub_simple_mirror() to
scrub_stripe infrastructure"), which is around 6.4).

So if "btrfs check --check-data-csum" shows no error, it would be a
false alert and you can just ignore them for now.

Thanks,
Qu
>
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242230988800 on dev /dev/mapper/slash3 physical 914556321792
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242227580928 on dev /dev/mapper/slash3 physical 914555469824
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242228105216 on dev /dev/mapper/slash3 physical 914555600896
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242230202368 on dev /dev/mapper/slash3 physical 914556125184
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242233348096 on dev /dev/mapper/slash3 physical 914556911616
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242227843072 on dev /dev/mapper/slash3 physical 914555535360
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242228367360 on dev /dev/mapper/slash3 physical 914555666432
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242229415936 on dev /dev/mapper/slash3 physical 914555928576
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242229940224 on dev /dev/mapper/slash3 physical 914556059648
> BTRFS error (device dm-0): unable to fixup (regular) error at logical
> 7242228891648 on dev /dev/mapper/slash3 physical 914555797504
> BTRFS warning (device dm-0): checksum error at logical 7242227843072
> on dev /dev/mapper/slash3, physical 914555535360, root 136483, inode
> 60736199, offset 720896, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242228891648
> on dev /dev/mapper/slash3, physical 914555797504, root 136483, inode
> 60736199, offset 1769472, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242228105216
> on dev /dev/mapper/slash3, physical 914555600896, root 136483, inode
> 60736199, offset 983040, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242228367360
> on dev /dev/mapper/slash3, physical 914555666432, root 136483, inode
> 60736199, offset 1245184, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242230988800
> on dev /dev/mapper/slash3, physical 914556321792, root 136483, inode
> 60736199, offset 3866624, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242229940224
> on dev /dev/mapper/slash3, physical 914556059648, root 136483, inode
> 60736199, offset 2818048, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242228891648
> on dev /dev/mapper/slash3, physical 914555797504, root 136483, inode
> 60736199, offset 1769472, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242233348096
> on dev /dev/mapper/slash3, physical 914556911616, root 136483, inode
> 60736199, offset 6225920, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242230202368
> on dev /dev/mapper/slash3, physical 914556125184, root 136483, inode
> 60736199, offset 3080192, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> BTRFS warning (device dm-0): checksum error at logical 7242227843072
> on dev /dev/mapper/slash3, physical 914555535360, root 136483, inode
> 60736199, offset 720896, length 4096, links 1 (path:
> var/cache/pacman/pkg/agda-2.6.3-27-x86_64.pkg.tar.zst)
> scrub_stripe_report_errors: 344892 callbacks suppressed
> ...
>

  reply	other threads:[~2024-02-26  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 19:30 Corruption while bisecting (was: [PATCH] btrfs: tree-checker: dump the page status if hit something wrong) Tavian Barnes
2024-02-26  8:30 ` Qu Wenruo [this message]
2024-02-26 15:49   ` Tavian Barnes
2024-02-26 15:56     ` David Sterba
2024-02-26 15:53 ` David Sterba
2024-02-26 16:03   ` Tavian Barnes

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=f9296554-9c90-4991-a67e-d1a8defafca3@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tavianator@tavianator.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox