From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: kworker/u32:5+btrfs-delalloc using 100% CPU
Date: Fri, 03 Dec 2021 09:16:59 +0100 [thread overview]
Message-ID: <93111e00ad2e42738d65d426f82ad17f@wpkg.org> (raw)
In-Reply-To: <PH0PR04MB7416465C59F5F339FA87AB839B6A9@PH0PR04MB7416.namprd04.prod.outlook.com>
On 2021-12-03 09:09, Johannes Thumshirn wrote:
> On 03/12/2021 00:23, Tomasz Chmielewski wrote:
>> On two of my servers running Linux 5.15.5 I can observe
>> kworker/u32:5+btrfs-delalloc process using 100% CPU.
>>
>> The servers receive files with rsync and I suspect that because of
>> that
>> process using 100% CPU, the speed is very slow, less than 1 MB/s over
>> a
>> gigabit network.
>>
>
> Hi,
>
> We're currently working on a similar hang with btrfs on zoned
> block devices. Which brings me to the question, are you seeing this
> issues
> on a zoned device, like an SMR drive, or on a regular device?
It's a regular HDD.
Tomasz
next prev parent reply other threads:[~2021-12-03 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 23:16 kworker/u32:5+btrfs-delalloc using 100% CPU Tomasz Chmielewski
2021-12-03 8:09 ` Johannes Thumshirn
2021-12-03 8:16 ` Tomasz Chmielewski [this message]
2021-12-03 17:23 ` Chris Murphy
2021-12-03 18:05 ` Chris Murphy
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=93111e00ad2e42738d65d426f82ad17f@wpkg.org \
--to=mangoo@wpkg.org \
--cc=Johannes.Thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox