From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Sun 22 Jun 2003 - 11:48:55 BST
On Sun, Jun 22, 2003 at 09:11:56AM +0200, Roland Moriz wrote:
> Hi Nuno,
> Am Son, 2003-06-22 um 06.49 schrieb Nuno Silva:
> > The, very simple, way of doing this is creating a 1GB file, mkfs it and
> > mount it in the /vserver/NAME just before vserver NAME start (read the
> > docs to find out a way of doing this automatically).
> > This limits the vserver's size, only. The advantage is that's a simple
> > procedure and nothing more is required. AS always, IMMV.
> that sounds like a very practicable solution since i only need size
> limiting for complete vserver environments. I'll try your method if I
> don't get vroot/vquota working that way.
although this might sound like a 'very practicable' solution
you should be aware of the drawbacks:
- loop filesystems are 'lazy' (cached) so your files
in the vserver will be cached twice, and writebacks
within the filesystem will not be synchronous
what does that mean? you lose memory, and on power
failure/reboot you _will_ lose data ...
(this is much better with lvm volumes)
- unification can not be used across devices
what does that mean? again you lose memory and
performance, because libraries and common
executables can not be shared amongh vservers
(this holds for loop and lvm)
what are your issues with vquota?
I could not find any question/problem to answer in
your postings yet ...
> thank you,
> with kind regards,
> Mit freundlichen Gruessen,
> Roland Moriz
> Muenchen/Germany - http://www.roland-moriz.de/