On 09/28/2011 12:24 AM, Alessandro Ghedini wrote: >> Issue 1: >> > ERROR: can't mount: /sys/fs/cgroup/cpu >> > aborting... >> > >> > >> > If cgroup is already mounted (in fstab), ulatencyd fails with the above >> > message. Looks like on startup, it tries to mount cgroup. > It sound like the correct behaviour to me. AFAIK if the target directory is > already mounted there's no way to gracefully handle the error (and yes, > ulatencyd mounts the cgroups). Just to make sure I'll contact the upstream > author to hear what he thinks. >
There's another side-effect of this. If I let ulatencyd handle the mount, it breaks my linux containers setup. I haven't investigated in detail, but just fyi. 01:25:57 rrs@champaran:/usr/share/doc/lxc$ sudo lxc-start --name deb-server [sudo] password for rrs: lxc-start: cgroup is not mounted lxc-start: failed to setup the cgroups for 'deb-server' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'deb-server' lxc-start: Device or resource busy - failed to remove cgroup '/sys/fs/cgroup/cpu/deb-server' mount does not report any cgroup mount points. The one that'd have been mounted by ulatencyd. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
