From: Matthew Wilcox <matthew@wil.cx>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] vfs generic subtree support
Date: Tue, 16 Feb 2010 08:12:58 -0700 [thread overview]
Message-ID: <20100216151257.GK11239@parisc-linux.org> (raw)
In-Reply-To: <87hbphns33.fsf@openvz.org>
On Tue, Feb 16, 2010 at 06:00:32PM +0300, Dmitry Monakhov wrote:
> Use-cases:
> *Assing maximum disc space consumption for some hierarchy *
>
> 1) Create chroot environment
> # tar xf chroot_env.tar /var/xxx/chroot
> 2) Assign some metagroup id to the chroot content (via not yet
> existent ./metagroup cmd-tool)
> # find /var/xxx/chroot | xargs ./metagroup --set 1000
>
> 3) Setup quota limits
> # quota-set --type metagroup --blk_soft=1024M blk_hard=1024M /var
>
> 4) Export this tree (it may be more complex)
> # mount /var/xxx/chroot /mnt/chroot -obound
>
> 5)Now we may use this /mnt/chroot as:
> 5A) A regular chroot envirement, user is unable to exceed metagroup
> quota, regardless to real available space on /var/
> 5B) As a container's (namespace) root.
> 5C) export this /mnt/chroot to nfs server and nfs client can not
> overcome given metagroup quota limit.
This all seems quota-related ... do you envisage uses that aren't
quota-related?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2010-02-16 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 10:52 [RFC] vfs generic subtree support Dmitry Monakhov
2010-02-16 12:20 ` Al Viro
2010-02-16 12:37 ` Dmitry Monakhov
2010-02-16 13:38 ` Al Viro
2010-02-16 14:01 ` Dmitry Monakhov
2010-02-16 14:21 ` Al Viro
2010-02-16 15:00 ` Dmitry Monakhov
2010-02-16 15:12 ` Matthew Wilcox [this message]
2010-02-16 15:32 ` Dmitry Monakhov
2010-02-16 19:25 ` J. Bruce Fields
2010-02-16 19:32 ` Christoph Hellwig
2010-02-16 19:39 ` J. Bruce Fields
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=20100216151257.GK11239@parisc-linux.org \
--to=matthew@wil.cx \
--cc=dmonakhov@openvz.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).