public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>,
	Olivier Wuillemin <olivier@wuillemin.fr>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux btrfs <linux-btrfs@vger.kernel.org>
Subject: Fwd: Btrfs scrub on single ssd reports non existing errors on Linux 6.4
Date: Thu, 3 Aug 2023 21:20:54 +0700	[thread overview]
Message-ID: <36f891d3-0236-d3c7-55c8-0d8a73d4e30d@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> My distribution is a Manjaro 23.0.0, CPU is AMD A10.
> System disk is an SSD PNY_CS900 120Gb
> 
> With Linux 6.4.6.1-MANJARO, a scrub on then system disk root reports errors  and some times freeze the linux :
> 
> sudo btrfs scrub status /
> UUID:             53e62983-fed7-46ed-b97c-23d19af4f26f
> Scrub started:    Tue Aug  1 13:26:14 2023
> Status:           running
> Duration:         0:03:21
> Time left:        1:12:50
> ETA:              Tue Aug  1 14:42:25 2023
> Total to scrub:   85.39GiB
> Bytes scrubbed:   3.75GiB  (4.40%)
> Rate:             19.13MiB/s
> Error summary:    read=80
>   Corrected:      34
>   Uncorrectable:  46
>   Unverified:     0
> 
> In this case, this report is the last one before the Linux freeze.
> Scrub not always freese, but when it freeze only low level functionnalities as ping or ps are working.
> 
> If Y downgrade the linux kernel to 6.1.41-1-MANJARO there is no errors :
> 
> sudo btrfs scrub status /
> UUID:             53e62983-fed7-46ed-b97c-23d19af4f26f
> Scrub started:    Thu Aug  3 14:17:11 2023
> Status:           finished
> Duration:         0:04:41
> Total to scrub:   66.72GiB
> Rate:             225.62MiB/s
> Error summary:    no errors found
> 
> Ask me if you want more details.

See Bugzilla for the full thread.

Anyway, I'm adding this regression to be tracked by regzbot:

#regzbot introduced: v6.1.41..v6.4.6 https://bugzilla.kernel.org/show_bug.cgi?id=217758

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217758

-- 
An old man doll... just what I always wanted! - Clara

                 reply	other threads:[~2023-08-03 14:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=36f891d3-0236-d3c7-55c8-0d8a73d4e30d@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olivier@wuillemin.fr \
    --cc=regressions@lists.linux.dev \
    /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