From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 203887] New: CGroup writeback is not supported by `xfs` filesystem leading to errors when using containers.
Date: Thu, 13 Jun 2019 14:13:08 +0000 [thread overview]
Message-ID: <bug-203887-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203887
Bug ID: 203887
Summary: CGroup writeback is not supported by `xfs` filesystem
leading to errors when using containers.
Product: File System
Version: 2.5
Kernel Version: 4.14
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: axel.borja.login@gmail.com
Regression: No
I am currently working on a Kubernetes cluster, which uses docker.
This cluster allows me to launch jobs. For each job, I specify a memory request
and a memory limit.
The memory limit will be used by Kubernetes to fill the `--memory` option of
the docker run command when creating the container. If this container exceeds
this limit it will be killed for OOM reason.
When writing on disk, pages will be written-back on the RAM before being
written to the disk. To do this the system will evaluate how many pages could
be written-back using the sysctl `vm.dirty_ratio` (20 % by default) and memory
from the root cgroup.
In case of intensive IO operations, it leads some containers to OOM errors.
xfs should be able to writeback using cgroup.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2019-06-13 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 14:13 bugzilla-daemon [this message]
2019-06-13 14:15 ` [Bug 203887] CGroup writeback is not supported by `xfs` filesystem leading to errors when using containers 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-203887-201763@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox