From: Brian Foster <bfoster@redhat.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [Bug 207817] kworker using a lots of cpu
Date: Thu, 21 May 2020 13:09:54 -0400 [thread overview]
Message-ID: <20200521170954.GB45732@bfoster> (raw)
In-Reply-To: <bug-207817-201763-k4jOyZfee6@https.bugzilla.kernel.org/>
On Thu, May 21, 2020 at 04:45:34PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=207817
>
> --- Comment #1 from Alexander Petrovsky (askjuise@gmail.com) ---
> After 1 day, it seems like some internal activity calm down kworker at 00:00
> UTC, it could be logrotate or smth else. But now, I'm observe the follow (seems
> like it has the same root cause):
>
Note that you're reporting problems with a distro kernel and proprietary
hypervisor to an upstream mailing list (via an upstream bug tracker).
The feedback will likely be limited unless you can reproduce on an
upstream kernel.
In general, it's not really clear to me what you're reporting beyond the
writeback task using more CPU than anticipated. What is that based on?
What problematic functional or performance related behavior is observed?
If performance related, what exactly is the workload?
> #df -h
> Filesystem Size Used Avail Use% Mounted on
> ...
> /dev/mapper/vg_logs-lv_varlog 38G -30G 68G - /var/log
> ...
I think we've had some upstream patches to fix underflows and such in
space reporting paths fairly recently, but I'm not sure off hand if
those are associated with any functional issues beyond indication of
potential corruption. This suggests you should probably run 'xfs_repair
-n' on this filesystem if you haven't already.
Brian
>
> --
> You are receiving this mail because:
> You are watching the assignee of the bug.
>
next prev parent reply other threads:[~2020-05-21 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 8:22 [Bug 207817] New: kworker using a lot of cpu bugzilla-daemon
2020-05-21 16:45 ` [Bug 207817] kworker using a lots " bugzilla-daemon
2020-05-21 17:09 ` Brian Foster [this message]
2020-05-21 17:10 ` bugzilla-daemon
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=20200521170954.GB45732@bfoster \
--to=bfoster@redhat.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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