Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1188037 - Not able to write to memory.memsw.limit_in_bytes
Summary: Not able to write to memory.memsw.limit_in_bytes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zbigniew Jędrzejewski-Szmek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1187882 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-01 17:12 UTC by Dusty Mabe
Modified: 2015-02-25 00:24 UTC (History)
10 users (show)

Fixed In Version: systemd-216-20.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-15 03:05:34 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dusty Mabe 2015-02-01 17:12:09 UTC 
Description of problem:

Not able to write to memory.memsw.limit_in_bytes. Example:

-bash-4.3# rpm -q docker-io systemd
docker-io-1.4.1-5.fc21.x86_64
systemd-216-17.fc21.x86_64
-bash-4.3# docker run --rm --memory 500M busybox echo "I'm Alive"
FATA[0003] Error response from daemon: Cannot start container d79629bfddc7833497b612e2b6d4cc2542ce9a8c2253d39ace4434bbd385185b: write /sys/fs/cgroup/memory/system.slice/docker-d79629bfddc7833497b612e2b6d4cc2542ce9a8c2253d39ace4434bbd385185b.scope/memory.memsw.limit_in_bytes: invalid argument


This has been fixed by [1] and is somewhat documented in [2]. A full reproducer for F21 atomic host can be found at [3].

[1] - http://cgit.freedesktop.org/systemd/systemd/commit/?id=a3bd89ea99
[2] - https://github.com/docker/docker/issues/10280
[3] - http://dustymabe.com/2015/01/31/crisis-averted-im-using-atomic-host/
Comment 1 Zbigniew Jędrzejewski-Szmek 2015-02-05 20:23:57 UTC 
*** Bug 1187882 has been marked as a duplicate of this bug. ***
Comment 2 Fedora Update System 2015-02-05 20:53:25 UTC 
systemd-216-20.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/systemd-216-20.fc21
Comment 3 Fedora Update System 2015-02-07 03:57:30 UTC 
Package systemd-216-20.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-216-20.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-1793/systemd-216-20.fc21
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2015-02-15 03:05:34 UTC 
systemd-216-20.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 5 Nathan W 2015-02-25 00:22:33 UTC 
is this being backported to the systemd that ships in EL7 as well? we're definitely impacted on fully updated CentOS 7 running 208-11.el7_0.6.
Comment 6 Zbigniew Jędrzejewski-Szmek 2015-02-25 00:24:02 UTC 
Dunno. Ask in the CentOS bugtracker maybe.
Note You need to log in before you can comment on or make changes to this bug.