From: Martin Steigerwald <martin@lichtvoll.de>
To: Tim Cuthbertson <ratcheer@gmail.com>,
linux-btrfs@vger.kernel.org,
Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: Scrub of my nvme SSD has slowed by about 2/3
Date: Wed, 19 Jul 2023 08:42:58 +0200 [thread overview]
Message-ID: <3526703.iIbC2pHGDl@lichtvoll.de> (raw)
In-Reply-To: <1d611dbb-8aee-9a6e-701c-6498f1b51c34@leemhuis.info>
Hi Thorsten.
#regzbot monitor: https://lore.kernel.org/linux-btrfs/cover.1689744163.git.wqu@suse.com/
I hope that does it.
Above links to a patch of Qu about asking for other ideas to fix the
regression. It however has been superseded by a later patch of him.
So feel free to drop this.
Best,
Martin
Linux regression tracking #adding (Thorsten Leemhuis) - 12.07.23, 13:02:18 CEST:
> [CCing the regression list, as it should be in the loop for
> regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>
> [TLDR: I'm adding this report to the list of tracked Linux kernel
> regressions; the text you find below is based on a few templates
> paragraphs you might have encountered already in similar form.
> See link in footer if these mails annoy you.]
>
> On 03.07.23 22:19, Tim Cuthbertson wrote:
> > Yesterday, I noticed that a scrub of my main system filesystem has
> > slowed from about 2.9 gb/sec to about 949 mb/sec. My scrub used to
> > run in about 12 seconds, now it is taking 51 seconds. I had just
> > installed Linux kernel 6.4.1 on Arch Linux, upgrading from 6.3.9.
> > At first I suspected the new kernel, but now I am not so sure.
>
> Thanks for the report. It seems it will take some work to address
> this, so to be sure the issue doesn't fall through the cracks
> unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced e02ee89baa66
> #regzbot title btrfs: scrub nvme SSD has slowed by about 2/3 due to
> csum #regzbot monitor:
> https://lore.kernel.org/all/6c1ffe48e93fee9aa975ecc22dc2e7a1f3d7a0de.1
> 688539673.git.wqu@suse.com/ #regzbot ignore-activity
>
> This isn't a regression? This issue or a fix for it are already
> discussed somewhere else? It was fixed already? You want to clarify
> when the regression started to happen? Or point out I got the title
> or something else totally wrong? Then just reply and tell me --
> ideally while also telling regzbot about it, as explained by the page
> listed in the footer of this mail.
>
> Developers: When fixing the issue, remember to add 'Link:' tags
> pointing to the report (the parent of this mail). See page linked in
> footer for details.
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker'
> hat) --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> That page also explains what to do if mails like this annoy you.
--
Martin
next prev parent reply other threads:[~2023-07-19 6:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 20:19 Scrub of my nvme SSD has slowed by about 2/3 Tim Cuthbertson
2023-07-03 23:49 ` Qu Wenruo
2023-07-05 2:44 ` Qu Wenruo
2023-07-11 5:36 ` Martin Steigerwald
2023-07-11 5:33 ` Martin Steigerwald
2023-07-11 5:49 ` Martin Steigerwald
2023-07-11 5:52 ` Martin Steigerwald
2023-07-11 8:59 ` Qu Wenruo
2023-07-11 9:25 ` Martin Steigerwald
2023-07-11 9:57 ` Qu Wenruo
2023-07-11 10:56 ` Martin Steigerwald
2023-07-11 11:05 ` Qu Wenruo
2023-07-11 11:26 ` Martin Steigerwald
2023-07-11 11:33 ` Qu Wenruo
2023-07-11 11:47 ` Martin Steigerwald
2023-07-14 0:28 ` Qu Wenruo
2023-07-14 6:01 ` Qu Wenruo
2023-07-14 6:58 ` Martin Steigerwald
2023-07-16 9:57 ` Sebastian Döring
2023-07-16 10:55 ` Qu Wenruo
2023-07-16 16:01 ` Sebastian Döring
2023-07-17 5:23 ` Qu Wenruo
2023-07-12 11:02 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-07-19 6:42 ` Martin Steigerwald [this message]
2023-07-19 6:55 ` Martin Steigerwald
2023-08-29 12:17 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-09-08 11:54 ` Martin Steigerwald
2023-09-08 22:03 ` Qu Wenruo
2023-09-09 8:06 ` Martin Steigerwald
2023-10-13 13:07 ` Martin Steigerwald
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=3526703.iIbC2pHGDl@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=ratcheer@gmail.com \
--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 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.