From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 21 Sep 2004 - 13:19:58 BST
On Tue, Sep 21, 2004 at 07:24:22AM -0400, Marc E. Fiuczynski wrote:
> It works flawlessly, of course. My mistake was to give it a dev (as
> necessary for cq-tools) rather than a file in the fs as an argument.
so you created a dlimit entry for the filesystem the
device is on ... understandable ...
> Will import the util-vserver 0.30.193 code, merge the vdlimit.c file, and
> then send the diff to the mailing list (or just Enrico and you).
yeah, a 'solid' util-vserver (alpha) implementation
would be nice, but double-check with enrico, if that
isn't already work in progress ...
still I'm interested in the compile errors you got
with the vdlimit experimental tool ..
TIA,
Herbert
> Cheers,
> Marc
>
> -----Original Message-----
> From: Herbert Poetzl [mailto:herbert_at_13thfloor.at]
> Sent: Tuesday, September 21, 2004 3:07 AM
> To: Marc E. Fiuczynski
> Cc: vserver_at_list.linux-vserver.org
> Subject: Re: [Vserver] vdlimit
>
>
> On Mon, Sep 20, 2004 at 09:09:03PM -0400, Marc E. Fiuczynski wrote:
> > Hi,
> >
> > Was trying to get vdlimit to work. First, i grabbed the vdlimit 0.01 tar
> > ball from the Experimental area. Is that what I should grab?
>
> hmm, yes for 1.9.x ...
>
> > Any way, tried compiling it without much luck.
>
> interesting, any trace of the compile errors ...
>
> > Took the vdlimit.c file and integrated it with util-vserver 0.30.
>
> hmm, well, okay ... so be it ...
>
> > After some fiddling I got that compiled. It seems to
> > work on a 2.6.8.1 system with vserver 1.9.2---i.e., the
> > get_dlimit call appears to read back the value that I set.
>
> > However, when I enter the vserver and do a df, I don't
> > see the disklimit value that I set. What am I getting
> > wrong here?
>
> assumed that it really does work, you have tagxid
> enabled for the filesystem, the dlimit entry was
> added, and the limit set, then the df/df -i should
> adjust the values to 'match' the limits, i.e. it
> will reduce the available size to the minimum of
> available space and configured limit ...
>
> remember, values are
> blocks/max-blocks/inodes/max-inodes/root-reserve
> and don't forget to specify a path to the filesystem
>
> example:
>
> # mount -o tagxid /dev/discs/disc1/part1 /vservers
> # chcontext --ctx 100 df
> New security context is 100
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/root 31698 25243 6455 80% /
> /dev/discs/disc1/part1 253775 185884 54789 78% /vservers
>
> # vdlimit -a -x 100 -S 0,1000,0,100,10 /vservers
> # chcontext --ctx 100 df
> New security context is 100
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/root 31698 25243 6455 80% /
> /dev/discs/disc1/part1 1000 0 899 0% /vservers
>
> (vdlimit compiled on mandrake, then tested on
> 2.6.9-rc2-vs1.9.2.28.4 but should work since
> 1.9.2, even for some 1.9.1.x versions)
>
> HTH,
> Herbert
>
> > Marc
> >
> >
> >
> > _______________________________________________
> > Vserver mailing list
> > Vserver_at_list.linux-vserver.org
> > http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver