From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 207817] kworker using a lots of cpu
Date: Thu, 21 May 2020 16:45:34 +0000 [thread overview]
Message-ID: <bug-207817-201763-k4jOyZfee6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207817-201763@https.bugzilla.kernel.org/>
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):
#df -h
Filesystem Size Used Avail Use% Mounted on
...
/dev/mapper/vg_logs-lv_varlog 38G -30G 68G - /var/log
...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-05-21 16:45 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 ` bugzilla-daemon [this message]
2020-05-21 17:09 ` [Bug 207817] kworker using a lots " Brian Foster
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=bug-207817-201763-k4jOyZfee6@https.bugzilla.kernel.org/ \
--to=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 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.