From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: kt-S89nZTSLPHGGdvJs77BJ7Q@public.gmane.org
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
lxc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [lxc-devel] LXC quota support
Date: Tue, 01 Sep 2009 20:32:49 +0200 [thread overview]
Message-ID: <4A9D68D1.5030807@free.fr> (raw)
In-Reply-To: <ac1c4bf20909010930q5721c9bas2ea3722e94657820-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Krzysztof Taraszka wrote:
> Hello,
>
> I am looking for quota support for LXC containers. For example, I would like
> to have two containers. One of them may have 20GB, second 50GB.
> I found this one patch:
> https://lists.linux-foundation.org/pipermail/containers/2009-February/015807.htmland
> I have a question. Does there is another implemented method for have
> disk quota for container and his cgrop ? How about rootfs available disk
> space information ? If no, is there any ideas how to and when the disk quota
> will be implemented?
Anqui did a first try with this patch. The feature was positively
received but not in this form. I don't know what is the status of this
work, but maybe Anqui can give an answer :) - Cc'ed.
Anqui ? Did you tried to implement quotas with the directory hierarchy
level as suggested Paul ?
Krzysztof, one solution to restrict disk usage to a container can be to
create an disk image of 20GB, mount it on a directory, install the
rootfs on it and use this directory as the rootfs for the container.
-- Daniel
ps: The disk image should be a sparse file ;)
next prev parent reply other threads:[~2009-09-01 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 16:30 LXC quota support Krzysztof Taraszka
[not found] ` <ac1c4bf20909010930q5721c9bas2ea3722e94657820-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-01 18:32 ` Daniel Lezcano [this message]
[not found] ` <4A9D68D1.5030807-GANU6spQydw@public.gmane.org>
2009-09-03 2:53 ` [lxc-devel] " anqin
[not found] ` <d95d44a20909021953x7779a2dfpcc38e5915ae5515b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-03 8:49 ` Daniel Lezcano
[not found] ` <4A9F8320.6090001-GANU6spQydw@public.gmane.org>
2009-09-03 10:33 ` 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=4A9D68D1.5030807@free.fr \
--to=daniel.lezcano-ganu6spqydw@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=kt-S89nZTSLPHGGdvJs77BJ7Q@public.gmane.org \
--cc=lxc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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