[Bug 203887] New: CGroup writeback is not supported by `xfs` filesystem leading to errors when using containers.

[Bug 203887] New: CGroup writeback is not supported by `xfs` filesystem leading to errors when using containers.

[bugzilla-daemon]

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.

[Bug 203887] CGroup writeback is not supported by `xfs` filesystem leading to errors when using containers.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=203887

--- Comment #1 from axel.borja.login@gmail.com ---
My nodes are running under RHEL with a kernel 4.14 and I encounter OOM errors
when writing with xfs.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.