Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Dwight Schauer <dschauer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: lxc-start: Device or resource busy - failed to remove previous cgroup
Date: Mon, 4 Jan 2010 20:30:01 -0600	[thread overview]
Message-ID: <20100105023001.GA19747@us.ibm.com> (raw)
In-Reply-To: <68e6eac61001041815h251bf0ffi5123f42e69e6a179-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Quoting Dwight Schauer (dschauer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org):
> On Mon, Jan 4, 2010 at 7:24 PM, Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> wrote:
> > tasks is empty, but there are subdirectories - 102, 26533, etc.
> > This looks like the dirtywork of the ns cgroup.  If each of those
> > subdirs is also empty then you can rmdir them, then rmdir /cgroup/arch64-1.
> >
> > Or, use a release agent, which is what I do.
> >
> > cat << EOF > /bin/remove_dead_cgroup.sh
> > #!/bin/sh
> > echo "Removing dead cgroup .$*." >> /var/log/cgroup
> > rmdir /cgroup/$* >> /var/log/cgroup 2>&1
> > echo "return value was $?" >> /var/log/cgroup
> > EOF
> > echo /bin/remove_dead_cgroup.sh > /cgroup/release_agent
> > echo 1 > /cgroup/notify_on_release
> >
> 
> well, In my case those numbered subdirectories are empty, and I can't
> remove the files in them as root even with -f.
> 
> I'll try with a newer kernel.

By 'they are empty' you mean no tasks listed in their tasks file?
What files are you trying to rm -f?  So long as there are no further
cgroup subdirectories, just rmdir each directory - the cgroupfs files
can't be deleted by hand, it's true.

-serge

  parent reply	other threads:[~2010-01-05  2:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04  1:10 lxc-start: Device or resource busy - failed to remove previous cgroup Dwight Schauer
     [not found] ` <68e6eac61001031710w3e16f62blfb3b5bfb86ea43b7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-04  1:22   ` Balbir Singh
     [not found]     ` <661de9471001031722o21c6bd55kb73403c85a8145e3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-04  1:46       ` Dwight Schauer
     [not found]         ` <68e6eac61001031746r44668e6cheb497c7df5f68a18-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-04  2:54           ` Dwight Schauer
     [not found]             ` <4B41C5A4.704@free.fr>
     [not found]               ` <4B41C5A4.704-GANU6spQydw@public.gmane.org>
2010-01-04 15:21                 ` Dwight Schauer
     [not found]                   ` <68e6eac61001040721m250c0f14u9c07d04ef9ec3648-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-04 18:02                     ` Serge E. Hallyn
     [not found]                       ` <20100104180225.GA3510-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-05  0:42                         ` Dwight Schauer
     [not found]                           ` <68e6eac61001041642p15d34837ocd13f13bd8249f21-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-05  1:24                             ` Serge E. Hallyn
     [not found]                               ` <20100105012418.GA14928-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-05  2:15                                 ` Dwight Schauer
     [not found]                                   ` <68e6eac61001041815h251bf0ffi5123f42e69e6a179-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-05  2:30                                     ` Serge E. Hallyn [this message]
     [not found]             ` <68e6eac61001031854v35c9b0a0sebce033812977e73-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-04 15:57               ` Balbir Singh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100105023001.GA19747@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=dschauer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox