From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: anqin <anqin.qin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: Can not remove the subdirectory in cgroup pseudo-filesystem
Date: Wed, 25 Mar 2009 11:37:02 -0500 [thread overview]
Message-ID: <20090325163702.GA17626@us.ibm.com> (raw)
In-Reply-To: <d95d44a20903250924p2fb28afdq7ac47cac372c7de3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Quoting anqin (anqin.qin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org):
> Dear all,
>
> I have met a straight problem in my recent operation.
> Previously, I can do the following operations:
>
> # mount -t cgroup cgroup /mnt/cgrp
> # cd /mnt/cgrp
> # mkdir test
> # echo $$ > test/tasks
> # rm -rf test
I doubt this ever worked - rather, you have to do
rmdir test
rm -rf will try to delete the files under test/ first,
and fail.
>
> but now I met the straight permission with the same
> operation while I am root:
>
> # mount -t cgroup cgroup /mnt/cgrp
> # cd /mnt/cgrp
> # mkdir test
> # echo $$ > test/tasks
Yes you have to initialize some cpuset files first. Otherwise
the tasks have no access to any memory or cpus.
echo 0 > /cgroup/1/cpuset.mems
echo 0-3 > /cgroup/1/cpuset.cpus
echo $$ > /cgroup/1//tasks
(success)
> -bash: echo: write error: No space left on device
> # rm -rf test
> rm: cannot remove `/mnt/cgrp/test/cpuset.memory_spread_slab':
> Operation not permitted
> rm: cannot remove `/mnt/cgrp/test/cpuset.memory_spread_page':
> Operation not permitted
> rm: cannot remove `/mnt/cgrp/test/cpuset.memory_pressure': Operation
> not permitted
> ...
>
> I guess maybe the permission attributes block my operation, but I
> checked with lsattr
> and got the following message:
>
> # lsattr /mnt/cgrp/test
> lsattr: Inappropriate ioctl for device While reading flags on
> /mnt/cgrp/test/cpuset.memory_spread_slab
> lsattr: Inappropriate ioctl for device While reading flags on
> /mnt/cgrp/test/cpuset.memory_spread_page
> lsattr: Inappropriate ioctl for device While reading flags on
> /mnt/cgrp/test/cpuset.memory_pressure
> ...
>
> I have no idea how to fix it. Any help?
>
> Thank you very much,
>
> Anqin
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2009-03-25 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 16:24 Can not remove the subdirectory in cgroup pseudo-filesystem anqin
[not found] ` <d95d44a20903250924p2fb28afdq7ac47cac372c7de3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-25 16:37 ` Serge E. Hallyn [this message]
[not found] ` <20090325163702.GA17626-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-25 17:11 ` anqin
[not found] ` <d95d44a20903251011u5786c780wb3a0a0cc3b759689-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-26 1:15 ` Li Zefan
[not found] ` <49CAD714.4080307-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-03-26 1:51 ` Serge E. Hallyn
2009-03-27 3:06 ` anqin
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=20090325163702.GA17626@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=anqin.qin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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