Public bug reported:

When running lxc-top as root it flashes the following error messages for every 
container:
Unable to read cgroup item memory.memsw.usage_in_bytes
Unable to read cgroup item memory.memsw.limit_in_bytes

Here output showing bad blkio write
Container                   CPU          CPU          CPU                       
         BlkIO        Mem       KMem
Name                       Used          Sys         User                    
Total(Read/Write)       Used       Used
ltcd-root                310.22        98.26       196.88     315.06 MiB(315.06 
MiB/  0.00   ) 688.64 MiB  83.09 MiB
ltcd-test                236.02        84.52       136.76     115.88 MiB(115.88 
MiB/  0.00   ) 384.39 MiB  31.89 MiB
TOTAL 2 of 2             546.24       182.78       333.64     430.94 MiB(430.94 
MiB/  0.00   )   1.04 GiB 114.97 MiB


Doing an strace on lxc-top:

openat(AT_FDCWD, 
"/sys/fs/cgroup/memory//lxc/ltcd-root/memory.memsw.usage_in_bytes", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "Unable to read cgroup item memor"..., 55) = 55

openat(AT_FDCWD, 
"/sys/fs/cgroup/memory//lxc/ltcd-root/memory.memsw.limit_in_bytes", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "Unable to read cgroup item memor"..., 55) = 55

Here is copy /sys/fs/cgroup/memory/lxc/ltcd-root

mike@mike-desktop:/sys/fs/cgroup/memory/lxc/ltcd-root$ ls
cgroup.clone_children               memory.limit_in_bytes
cgroup.event_control                memory.max_usage_in_bytes
cgroup.procs                        memory.move_charge_at_immigrate
init.scope                          memory.numa_stat
memory.failcnt                      memory.oom_control
memory.force_empty                  memory.pressure_level
memory.kmem.failcnt                 memory.soft_limit_in_bytes
memory.kmem.limit_in_bytes          memory.stat
memory.kmem.max_usage_in_bytes      memory.swappiness
memory.kmem.slabinfo                memory.usage_in_bytes
memory.kmem.tcp.failcnt             memory.use_hierarchy
memory.kmem.tcp.limit_in_bytes      notify_on_release
memory.kmem.tcp.max_usage_in_bytes  system.slice
memory.kmem.tcp.usage_in_bytes      tasks
memory.kmem.usage_in_bytes          user.slice

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lxc-utils 3.0.3-0ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Jan 25 15:56:04 2019
InstallationDate: Installed on 2018-02-23 (336 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: Upgraded to bionic on 2018-10-21 (95 days ago)
mtime.conffile..etc.lxc.default.conf: 2019-01-24T17:40:41.527776

** Affects: lxc (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apparmor apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813362

Title:
  lxc-top flash error and blkio write is always zero

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1813362/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to