Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-22 Thread Miroslav Lednicky, AVONET, s.r.o.
Hello all,

i have the same problems with another servers in LXC.
It is really problem with vsftpd running in LXC container.

Do you have somebody similar problem with vsftpd in container?

Best regards,

Miroslav.

Dne 15.11.2010 16:17, Miroslav Lednicky, AVONET, s.r.o. napsal(a):
 Dne 15.11.2010 15:56, Daniel Lezcano napsal(a):
 On 11/15/2010 03:26 PM, Miroslav Lednicky, AVONET, s.r.o. wrote:
 Hello,

 please see:

 ls -l
 total 0
 drwxr-xr-x 4 root root 0 2010-11-15 15:00 1285
 drwxr-xr-x 4 root root 0 2010-11-15 15:00 1298
 drwxr-xr-x 4 root root 0 2010-11-15 15:01 1322
 drwxr-xr-x 4 root root 0 2010-11-15 15:01 1325
 drwxr-xr-x 4 root root 0 2010-11-15 15:02 1335
 drwxr-xr-x 4 root root 0 2010-11-15 15:09 1386
 drwxr-xr-x 4 root root 0 2010-11-15 15:11 1401
 drwxr-xr-x 4 root root 0 2010-11-15 15:12 1408
 drwxr-xr-x 4 root root 0 2010-11-15 15:12 1411
 drwxr-xr-x 3 root root 0 2010-11-15 15:17 1459
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cgroup.procs
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.usage
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.usage_percpu
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.rt_period_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.rt_runtime_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.cpu_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.cpus
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mem_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mem_hardwall
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_migrate
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_pressure
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_spread_page
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_spread_slab
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mems
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.sched_load_balance
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.sched_relax_domain_level
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.shares
 --w--- 1 root root 0 2010-11-15 15:02 devices.allow
 --w--- 1 root root 0 2010-11-15 15:02 devices.deny
 -r--r--r-- 1 root root 0 2010-11-15 15:02 devices.list
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 freezer.state
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.failcnt
 --w--- 1 root root 0 2010-11-15 15:02 memory.force_empty
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.max_usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.failcnt
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.max_usage_in_bytes
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.soft_limit_in_bytes
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.swappiness
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.use_hierarchy
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 net_cls.classid
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 notify_on_release
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 tasks
 r...@lnx-zl-teaspl:/cgroup/teas_www# ls -lR 1285
 1285:
 total 0
 drwxr-xr-x 2 root root 0 2010-11-15 15:00 2
 drwxr-xr-x 2 root root 0 2010-11-15 15:00 3
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cgroup.procs
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.usage
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.usage_percpu
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.rt_period_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.rt_runtime_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.cpu_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.cpus
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mem_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mem_hardwall
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_migrate
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_pressure
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_spread_page
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_spread_slab
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mems
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.sched_load_balance
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.sched_relax_domain_level
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.shares
 --w--- 1 root root 0 2010-11-15 15:00 devices.allow
 --w--- 1 root root 0 2010-11-15 15:00 devices.deny
 -r--r--r-- 1 root root 0 2010-11-15 15:00 devices.list
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 freezer.state
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.failcnt
 --w--- 1 root root 0 2010-11-15 15:00 memory.force_empty
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.limit_in_bytes
 -rw-r--r-- 1 

Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-15 Thread Miroslav Lednicky, AVONET, s.r.o.
Hello,

please see:

ls -l
total 0
drwxr-xr-x 4 root root 0 2010-11-15 15:00 1285
drwxr-xr-x 4 root root 0 2010-11-15 15:00 1298
drwxr-xr-x 4 root root 0 2010-11-15 15:01 1322
drwxr-xr-x 4 root root 0 2010-11-15 15:01 1325
drwxr-xr-x 4 root root 0 2010-11-15 15:02 1335
drwxr-xr-x 4 root root 0 2010-11-15 15:09 1386
drwxr-xr-x 4 root root 0 2010-11-15 15:11 1401
drwxr-xr-x 4 root root 0 2010-11-15 15:12 1408
drwxr-xr-x 4 root root 0 2010-11-15 15:12 1411
drwxr-xr-x 3 root root 0 2010-11-15 15:17 1459
-r--r--r-- 1 root root 0 2010-11-15 15:02 cgroup.procs
-r--r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.stat
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.usage
-r--r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.usage_percpu
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.rt_period_us
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.rt_runtime_us
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.cpu_exclusive
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.cpus
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mem_exclusive
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mem_hardwall
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_migrate
-r--r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_pressure
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_spread_page
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_spread_slab
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mems
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.sched_load_balance
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.sched_relax_domain_level
-rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.shares
--w--- 1 root root 0 2010-11-15 15:02 devices.allow
--w--- 1 root root 0 2010-11-15 15:02 devices.deny
-r--r--r-- 1 root root 0 2010-11-15 15:02 devices.list
-rw-r--r-- 1 root root 0 2010-11-15 15:02 freezer.state
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.failcnt
--w--- 1 root root 0 2010-11-15 15:02 memory.force_empty
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.limit_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.max_usage_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.failcnt
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.limit_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.max_usage_in_bytes
-r--r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.usage_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.soft_limit_in_bytes
-r--r--r-- 1 root root 0 2010-11-15 15:02 memory.stat
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.swappiness
-r--r--r-- 1 root root 0 2010-11-15 15:02 memory.usage_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.use_hierarchy
-rw-r--r-- 1 root root 0 2010-11-15 15:02 net_cls.classid
-rw-r--r-- 1 root root 0 2010-11-15 15:02 notify_on_release
-rw-r--r-- 1 root root 0 2010-11-15 15:02 tasks
r...@lnx-zl-teaspl:/cgroup/teas_www# ls -lR 1285
1285:
total 0
drwxr-xr-x 2 root root 0 2010-11-15 15:00 2
drwxr-xr-x 2 root root 0 2010-11-15 15:00 3
-r--r--r-- 1 root root 0 2010-11-15 15:00 cgroup.procs
-r--r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.stat
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.usage
-r--r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.usage_percpu
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.rt_period_us
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.rt_runtime_us
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.cpu_exclusive
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.cpus
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mem_exclusive
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mem_hardwall
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_migrate
-r--r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_pressure
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_spread_page
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_spread_slab
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mems
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.sched_load_balance
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.sched_relax_domain_level
-rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.shares
--w--- 1 root root 0 2010-11-15 15:00 devices.allow
--w--- 1 root root 0 2010-11-15 15:00 devices.deny
-r--r--r-- 1 root root 0 2010-11-15 15:00 devices.list
-rw-r--r-- 1 root root 0 2010-11-15 15:00 freezer.state
-rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.failcnt
--w--- 1 root root 0 2010-11-15 15:00 memory.force_empty
-rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.limit_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.max_usage_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.failcnt
-rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.limit_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.max_usage_in_bytes
-r--r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.usage_in_bytes
-rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.soft_limit_in_bytes
-r--r--r-- 1 root root 0 2010-11-15 15:00 memory.stat
-rw-r--r-- 1 root root 0 

Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-15 Thread Daniel Lezcano
On 11/15/2010 03:26 PM, Miroslav Lednicky, AVONET, s.r.o. wrote:
 Hello,

 please see:

 ls -l
 total 0
 drwxr-xr-x 4 root root 0 2010-11-15 15:00 1285
 drwxr-xr-x 4 root root 0 2010-11-15 15:00 1298
 drwxr-xr-x 4 root root 0 2010-11-15 15:01 1322
 drwxr-xr-x 4 root root 0 2010-11-15 15:01 1325
 drwxr-xr-x 4 root root 0 2010-11-15 15:02 1335
 drwxr-xr-x 4 root root 0 2010-11-15 15:09 1386
 drwxr-xr-x 4 root root 0 2010-11-15 15:11 1401
 drwxr-xr-x 4 root root 0 2010-11-15 15:12 1408
 drwxr-xr-x 4 root root 0 2010-11-15 15:12 1411
 drwxr-xr-x 3 root root 0 2010-11-15 15:17 1459
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cgroup.procs
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.usage
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.usage_percpu
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.rt_period_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.rt_runtime_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.cpu_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.cpus
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mem_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mem_hardwall
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_migrate
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_pressure
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_spread_page
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_spread_slab
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mems
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.sched_load_balance
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.sched_relax_domain_level
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.shares
 --w--- 1 root root 0 2010-11-15 15:02 devices.allow
 --w--- 1 root root 0 2010-11-15 15:02 devices.deny
 -r--r--r-- 1 root root 0 2010-11-15 15:02 devices.list
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 freezer.state
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.failcnt
 --w--- 1 root root 0 2010-11-15 15:02 memory.force_empty
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.max_usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.failcnt
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.max_usage_in_bytes
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.soft_limit_in_bytes
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.swappiness
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.use_hierarchy
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 net_cls.classid
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 notify_on_release
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 tasks
 r...@lnx-zl-teaspl:/cgroup/teas_www# ls -lR 1285
 1285:
 total 0
 drwxr-xr-x 2 root root 0 2010-11-15 15:00 2
 drwxr-xr-x 2 root root 0 2010-11-15 15:00 3
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cgroup.procs
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.usage
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.usage_percpu
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.rt_period_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.rt_runtime_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.cpu_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.cpus
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mem_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mem_hardwall
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_migrate
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_pressure
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_spread_page
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_spread_slab
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mems
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.sched_load_balance
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.sched_relax_domain_level
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.shares
 --w--- 1 root root 0 2010-11-15 15:00 devices.allow
 --w--- 1 root root 0 2010-11-15 15:00 devices.deny
 -r--r--r-- 1 root root 0 2010-11-15 15:00 devices.list
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 freezer.state
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.failcnt
 --w--- 1 root root 0 2010-11-15 15:00 memory.force_empty
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.max_usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.failcnt
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.max_usage_in_bytes
 -r--r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.usage_in_bytes
 

Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-15 Thread Daniel Lezcano
On 11/15/2010 04:17 PM, Miroslav Lednicky, AVONET, s.r.o. wrote:
 Dne 15.11.2010 15:56, Daniel Lezcano napsal(a):
 On 11/15/2010 03:26 PM, Miroslav Lednicky, AVONET, s.r.o. wrote:
 Hello,

 please see:

 ls -l
 total 0
 drwxr-xr-x 4 root root 0 2010-11-15 15:00 1285
 drwxr-xr-x 4 root root 0 2010-11-15 15:00 1298
 drwxr-xr-x 4 root root 0 2010-11-15 15:01 1322
 drwxr-xr-x 4 root root 0 2010-11-15 15:01 1325
 drwxr-xr-x 4 root root 0 2010-11-15 15:02 1335
 drwxr-xr-x 4 root root 0 2010-11-15 15:09 1386
 drwxr-xr-x 4 root root 0 2010-11-15 15:11 1401
 drwxr-xr-x 4 root root 0 2010-11-15 15:12 1408
 drwxr-xr-x 4 root root 0 2010-11-15 15:12 1411
 drwxr-xr-x 3 root root 0 2010-11-15 15:17 1459
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cgroup.procs
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.usage
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuacct.usage_percpu
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.rt_period_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.rt_runtime_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.cpu_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.cpus
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mem_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mem_hardwall
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_migrate
 -r--r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_pressure
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_spread_page
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.memory_spread_slab
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.mems
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpuset.sched_load_balance
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 
 cpuset.sched_relax_domain_level
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 cpu.shares
 --w--- 1 root root 0 2010-11-15 15:02 devices.allow
 --w--- 1 root root 0 2010-11-15 15:02 devices.deny
 -r--r--r-- 1 root root 0 2010-11-15 15:02 devices.list
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 freezer.state
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.failcnt
 --w--- 1 root root 0 2010-11-15 15:02 memory.force_empty
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.max_usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.failcnt
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 
 memory.memsw.max_usage_in_bytes
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.memsw.usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.soft_limit_in_bytes
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.swappiness
 -r--r--r-- 1 root root 0 2010-11-15 15:02 memory.usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 memory.use_hierarchy
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 net_cls.classid
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 notify_on_release
 -rw-r--r-- 1 root root 0 2010-11-15 15:02 tasks
 r...@lnx-zl-teaspl:/cgroup/teas_www# ls -lR 1285
 1285:
 total 0
 drwxr-xr-x 2 root root 0 2010-11-15 15:00 2
 drwxr-xr-x 2 root root 0 2010-11-15 15:00 3
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cgroup.procs
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.stat
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.usage
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuacct.usage_percpu
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.rt_period_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.rt_runtime_us
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.cpu_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.cpus
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mem_exclusive
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mem_hardwall
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_migrate
 -r--r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_pressure
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_spread_page
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.memory_spread_slab
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.mems
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpuset.sched_load_balance
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 
 cpuset.sched_relax_domain_level
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 cpu.shares
 --w--- 1 root root 0 2010-11-15 15:00 devices.allow
 --w--- 1 root root 0 2010-11-15 15:00 devices.deny
 -r--r--r-- 1 root root 0 2010-11-15 15:00 devices.list
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 freezer.state
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.failcnt
 --w--- 1 root root 0 2010-11-15 15:00 memory.force_empty
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.limit_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.max_usage_in_bytes
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.failcnt
 -rw-r--r-- 1 root root 0 2010-11-15 15:00 memory.memsw.limit_in_bytes
 -rw-r--r-- 1 root root 0 

Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-08 Thread Daniel Lezcano
On 11/05/2010 09:27 PM, Serge E. Hallyn wrote:
 Quoting Miroslav Lednicky (ledni...@avonet.cz):

 Hello,

  it is the same problem as I have may be:

 http://sourceforge.net/mailarchive/forum.php?thread_name=4CD297E2.2030806%40avonet.czforum_name=lxc-users

 I don't know what can I do with it.

 Server reboot is necessary ...
  
 I fired off a container and did a bunch of ns_exec's under it to create
 some cgroup subdirectories.  When I powered off the container, lxc did
 indeed complain about not being able to remove /cgroup/ubuntu1.  I did

   find /cgroup/ubuntu1 -type d -print0 | xargs -0 rmdir

 which deleted the subdirectories and complainted about not being able
 to remove ubuntu1 itself.  Then I did 'rmdir /cgroup/ubuntu1' and it
 worked.

 So the only problem with my find statement is that it doesn't work
 depth-first, so you might have to do it a few times to get all of the
 subdirectories.

 Daniel, I think it would be worthwhile for lxc, on exiting a container,
 to do a depth-first search or all directories under the container's
 cgroup, and rmdir them all.  What do you think?


Yep, agree.


--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-08 Thread Serge Hallyn
Quoting Brian K. White (br...@aljex.com):
 But also, since upgrading to kernel 2.6.36 (and already using lxc 0.7.2) 
 I haven't had to delete any cgroups manually anyways. It's probably not 
 my release_agent because I just noticed I didn't have a working 
 release_agent (no output in it's log, probably because the script wasn't 
 chmod 755)
 
 It's only been a couple days and only a few starts/stops while working 
 on a new start/stop/status init script though.

Hm, really?  Can you please let me know if that continues to be the
case?  If it is, then I won't bother with a patch for lxc.  Really,
since it'll drop ns cgroup support anyway, I suppose the patch might
not be worthwhile anyway.

(I ran my test on a 2.6.35 kernel)

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-08 Thread Brian K. White
On 11/8/2010 1:32 PM, Serge Hallyn wrote:
 Quoting Brian K. White (br...@aljex.com):
 But also, since upgrading to kernel 2.6.36 (and already using lxc 0.7.2)
 I haven't had to delete any cgroups manually anyways. It's probably not
 my release_agent because I just noticed I didn't have a working
 release_agent (no output in it's log, probably because the script wasn't
 chmod 755)

 It's only been a couple days and only a few starts/stops while working
 on a new start/stop/status init script though.

 Hm, really?  Can you please let me know if that continues to be the
 case?  If it is, then I won't bother with a patch for lxc.  Really,
 since it'll drop ns cgroup support anyway, I suppose the patch might
 not be worthwhile anyway.

 (I ran my test on a 2.6.35 kernel)


I might be full of crap. I forgot that I had added the find -delete 
command in the and of the stop) section of my new lxc init script, I 
will test more diligently and report back.

-- 
bkw

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Serge E. Hallyn
A few comments:

1. To remove the directories, rmdir all descendent directories.  I'd
   think something like 'find . -type d -print0 | xargs rmdir' would
   do.
2. You can prevent this from happening by using a notify-on-release
   handler.
3. This should stop happening when lxc (soon) switches to using the
   clone-child cgroup helper instead of the ns cgroup.

-serge

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Brian K. White
On 11/5/2010 1:34 PM, Serge E. Hallyn wrote:
 A few comments:

 1. To remove the directories, rmdir all descendent directories.  I'd
 think something like 'find . -type d -print0 | xargs rmdir' would
 do.

I can't delete _anything_ in there. Not a file, let alone a directory 
with or without files. Of course I tried that.

 2. You can prevent this from happening by using a notify-on-release
 handler.

How will it delete a file I can not? But I do remember the discussion 
about that a while ago and I did forget to set that up on this new box 
so I'll do that also, but I can't see how it will fix the root problem 
of not being able to delete the files.

 3. This should stop happening when lxc (soon) switches to using the
 clone-child cgroup helper instead of the ns cgroup.

Here's hoping. Thanks.

-- 
bkw

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Brian K. White
On 11/5/2010 1:34 PM, Serge E. Hallyn wrote:
 A few comments:

 1. To remove the directories, rmdir all descendent directories.  I'd
 think something like 'find . -type d -print0 | xargs rmdir' would
 do.
 2. You can prevent this from happening by using a notify-on-release
 handler.
 3. This should stop happening when lxc (soon) switches to using the
 clone-child cgroup helper instead of the ns cgroup.

 -serge


Just to make it clear...

nj9:~ # lxc-stop -n nj10-014
nj9:~ # lxc-info -n nj10-014
'nj10-014' is STOPPED
nj9:~ # lxc-destroy -n nj10-014
'nj10-014' does not exist
nj9:~ # lxc-ps -elf |grep nj10-014
0 S root  3037 32341  0  80   0 -   579 pipe_w 14:25 
pts/400:00:00 grep nj10-014
nj9:~ #
nj9:~ # rm -vrf /cgroup/nj10-014
rm: cannot remove `/cgroup/nj10-014/19237/3/cpuset.memory_spread_slab': 
Operation not permitted
rm: cannot remove `/cgroup/nj10-014/19237/3/cpuset.memory_spread_page': 
Operation not permitted
[...]
rm: cannot remove `/cgroup/nj10-014/net_cls.classid': Operation not 
permitted
rm: cannot remove `/cgroup/nj10-014/notify_on_release': Operation not 
permitted
rm: cannot remove `/cgroup/nj10-014/tasks': Operation not permitted
nj9:~ #

I don't know how to track down if there is possibly some process that is 
part of the cgroup even though lxc-ps doesn't show any.
Examine every single process and verify that it's part of the host or 
another container until I find one I can't account for?

Since this happens to me all the time and on different hosts (albeit 
using the same kernel versions and other software all configured the 
same way) I can't believe this doesn't happen to many others and I'm 
surprised I don't see more acknowledgment of the issue here. I see other 
people reporting the problem, but I also see the responses simply say to 
delete the files, which, we can't do.

So i wonder is my configuration and usage simply wrong? I'm using very 
simple config files copied from the veth samples.

nj9:~ # find /etc/lxc/nj10-010 -type f |xargs -tn1 cat
cat /etc/lxc/nj10-010/fstab
none /lxc/nj10-010/dev/pts devpts defaults 0 0
none /lxc/nj10-010/procproc   defaults 0 0
none /lxc/nj10-010/sys sysfs  defaults 0 0
none /lxc/nj10-010/dev/shm tmpfs  defaults 0 0
cat /etc/lxc/nj10-010/config
lxc.utsname = nj10-010
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.hwaddr = 02:00:47:bb:ce:56
lxc.network.ipv4 = 71.187.206.86/24
lxc.network.name = eth0
lxc.mount = /etc/lxc/nj10-010/fstab
lxc.rootfs = /lxc/nj10-010
nj9:~ #


How are you not having the same problem?

-- 
bkw

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Miroslav Lednicky
Hello,

it is the same problem as I have may be:

http://sourceforge.net/mailarchive/forum.php?thread_name=4CD297E2.2030806%40avonet.czforum_name=lxc-users

I don't know what can I do with it.

Server reboot is necessary ...

I have Ubuntu 10.04 x64 server.

Best regards,

Miroslav.

Dne 5.11.2010 18:14, Brian K. White napsal(a):
 I have lxc 0.7.2 on openSUSE 11.2, which is kernel 2.6.31

 I get this all the time on my other boxes which up to now have been lxc
 0.6.5 on the same kernel, but I've lived with it by just trying to never
 reboot containers, and only using containers for services that can stand
 to be rebooted so that I can actually reboot the host and thus all
 containers if I have to.

 Now I have a few containers on another box with lxc 0.7.2 and the user
 of one of the containers tried to reboot his vps and it can't restart
 because there are cgroups files that can't be deleted. tasks file is
 empty in that cgroups directory,
 nj9:~ # cat /cgroup/nj10-014/tasks |od
 000
 nj9:~ #
 but there are several pid subdirectories with files in each. They can't
 be deleted.
 lxc-ps -elf shows no processes in that container.

 lxc-ls shows no containers at all, although definitely one other
 container is running and working and has processes in lxc-ps.

 And I can't really reboot the host this time without telling a lot of
 paying customers to get out and stop working for a while.

 I could probably get this container back up temporarily by just renaming
 it so it doesn't collide with the stale cgroups files, but the question
 is, I thought this was fixed? was it a kernel bug and I need a newer
 kernel to clear this up ?



--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Serge E. Hallyn
Quoting Brian K. White (br...@aljex.com):
 On 11/5/2010 1:34 PM, Serge E. Hallyn wrote:
  A few comments:
 
  1. To remove the directories, rmdir all descendent directories.  I'd
  think something like 'find . -type d -print0 | xargs rmdir' would
  do.
 
 I can't delete _anything_ in there. Not a file, let alone a directory 
 with or without files. Of course I tried that.

Yes, I assumed so.  My point was that you can't delete files.  You can
only do a simple rmdir on the cgroup directory itself.

-serge

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Serge E. Hallyn
Quoting Brian K. White (br...@aljex.com):
 I don't know how to track down if there is possibly some process that is 
 part of the cgroup even though lxc-ps doesn't show any.
 Examine every single process and verify that it's part of the host or 
 another container until I find one I can't account for?

Does find /cgroup -name tasks -print0 | xargs cat show anything?

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Serge E. Hallyn
Quoting Miroslav Lednicky (ledni...@avonet.cz):
 Hello,
 
   it is the same problem as I have may be:
 
 http://sourceforge.net/mailarchive/forum.php?thread_name=4CD297E2.2030806%40avonet.czforum_name=lxc-users
 
 I don't know what can I do with it.
 
 Server reboot is necessary ...

I fired off a container and did a bunch of ns_exec's under it to create
some cgroup subdirectories.  When I powered off the container, lxc did
indeed complain about not being able to remove /cgroup/ubuntu1.  I did

find /cgroup/ubuntu1 -type d -print0 | xargs -0 rmdir

which deleted the subdirectories and complainted about not being able
to remove ubuntu1 itself.  Then I did 'rmdir /cgroup/ubuntu1' and it
worked.

So the only problem with my find statement is that it doesn't work
depth-first, so you might have to do it a few times to get all of the
subdirectories.

Daniel, I think it would be worthwhile for lxc, on exiting a container,
to do a depth-first search or all directories under the container's
cgroup, and rmdir them all.  What do you think?

-serge

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Brian K. White
On 11/5/2010 4:20 PM, Serge E. Hallyn wrote:
 Quoting Brian K. White (br...@aljex.com):
 I don't know how to track down if there is possibly some process that is
 part of the cgroup even though lxc-ps doesn't show any.
 Examine every single process and verify that it's part of the host or
 another container until I find one I can't account for?

 Does find /cgroup -name tasks -print0 | xargs cat show anything?


It shows a bezillion things, but what does that prove?

Did you mean just for the bad container?

find /cgroup/nj10-014 -name tasks -print0 | xargs -0 cat
produces no output.

This is a clearer picture:

nj9:~ # find /cgroup/nj10-014 -name tasks -print0 | xargs -t0n1 cat
cat /cgroup/nj10-014/19237/3/tasks
cat /cgroup/nj10-014/19237/2/tasks
cat /cgroup/nj10-014/19237/tasks
cat /cgroup/nj10-014/19206/3/tasks
cat /cgroup/nj10-014/19206/2/tasks
cat /cgroup/nj10-014/19206/tasks
cat /cgroup/nj10-014/19064/3/tasks
cat /cgroup/nj10-014/19064/2/tasks
cat /cgroup/nj10-014/19064/tasks
cat /cgroup/nj10-014/19061/2/tasks
cat /cgroup/nj10-014/19061/tasks
cat /cgroup/nj10-014/19056/2/tasks
cat /cgroup/nj10-014/19056/tasks
cat /cgroup/nj10-014/16826/2/tasks
cat /cgroup/nj10-014/16826/tasks
cat /cgroup/nj10-014/16818/2/tasks
cat /cgroup/nj10-014/16818/tasks
cat /cgroup/nj10-014/6363/2/tasks
cat /cgroup/nj10-014/6363/tasks
cat /cgroup/nj10-014/6360/2/tasks
cat /cgroup/nj10-014/6360/tasks
cat /cgroup/nj10-014/2845/2/tasks
cat /cgroup/nj10-014/2845/tasks
cat /cgroup/nj10-014/2842/2/tasks
cat /cgroup/nj10-014/2842/tasks
cat /cgroup/nj10-014/tasks
nj9:~ #

nj9:~ # find /cgroup/nj10-014 -name tasks -print0 | xargs -0 ls -l
-rw-r--r-- 1 root root 0 2010-11-03 09:36 /cgroup/nj10-014/16818/2/tasks
-rw-r--r-- 1 root root 0 2010-11-03 09:36 /cgroup/nj10-014/16818/tasks
-rw-r--r-- 1 root root 0 2010-11-03 09:38 /cgroup/nj10-014/16826/2/tasks
-rw-r--r-- 1 root root 0 2010-11-03 09:38 /cgroup/nj10-014/16826/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:38 /cgroup/nj10-014/19056/2/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:38 /cgroup/nj10-014/19056/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:38 /cgroup/nj10-014/19061/2/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:38 /cgroup/nj10-014/19061/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:38 /cgroup/nj10-014/19064/2/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:38 /cgroup/nj10-014/19064/3/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:38 /cgroup/nj10-014/19064/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:40 /cgroup/nj10-014/19206/2/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:40 /cgroup/nj10-014/19206/3/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:40 /cgroup/nj10-014/19206/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:40 /cgroup/nj10-014/19237/2/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:40 /cgroup/nj10-014/19237/3/tasks
-rw-r--r-- 1 root root 0 2010-11-03 15:40 /cgroup/nj10-014/19237/tasks
-rw-r--r-- 1 root root 0 2010-11-01 18:27 /cgroup/nj10-014/2842/2/tasks
-rw-r--r-- 1 root root 0 2010-11-01 18:27 /cgroup/nj10-014/2842/tasks
-rw-r--r-- 1 root root 0 2010-11-01 18:27 /cgroup/nj10-014/2845/2/tasks
-rw-r--r-- 1 root root 0 2010-11-01 18:27 /cgroup/nj10-014/2845/tasks
-rw-r--r-- 1 root root 0 2010-11-01 22:06 /cgroup/nj10-014/6360/2/tasks
-rw-r--r-- 1 root root 0 2010-11-01 22:06 /cgroup/nj10-014/6360/tasks
-rw-r--r-- 1 root root 0 2010-11-01 22:08 /cgroup/nj10-014/6363/2/tasks
-rw-r--r-- 1 root root 0 2010-11-01 22:08 /cgroup/nj10-014/6363/tasks
-rw-r--r-- 1 root root 0 2010-11-01 18:04 /cgroup/nj10-014/tasks
nj9:~ #

! wait, you are saying just ignore the fact that there are files in 
the directories and try to remove the directories, uh directly?

nj9:~ # find /cgroup/nj10-014 -type d -delete
nj9:~ # ls -lR /cgroup/nj10-014
ls: cannot access /cgroup/nj10-014: No such file or directory


 It never even slightly occured to me to try that!

Thanks! Now I know what to put in the release agent too. Awsome. Thanks 
again.

-- 
bkw

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] can't restart container without rebooting entire host, because can't delete cgroups files, tasks is 0

2010-11-05 Thread Serge E. Hallyn
Quoting Brian K. White (br...@aljex.com):
 ! wait, you are saying just ignore the fact that there are files in 
 the directories and try to remove the directories, uh directly?
 
 nj9:~ # find /cgroup/nj10-014 -type d -delete
 nj9:~ # ls -lR /cgroup/nj10-014
 ls: cannot access /cgroup/nj10-014: No such file or directory
 
 
  It never even slightly occured to me to try that!
 
 Thanks! Now I know what to put in the release agent too. Awsome. Thanks 
 again.

Sorry, I should have said that more explicitly from the start, because
clearly it's not something a reasonable person would expect.

And I do think lxc should clean that up.  If I get a moment next
week I'll whip up a patch.

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users