From: Gregory (Grisha) Trubetskoy (grisha_at_ispol.com)
Date: Fri 19 Mar 2004 - 00:07:45 GMT
OK, I figured it out.
I guess it really helps not to have CONFIG_INOXID_NONE in the kernel
config. (Or in other words "Persistent Context ID for files" options in
make menuconfig).
Sorry for the confusion!
Grisha
On Thu, 18 Mar 2004, Herbert Poetzl wrote:
> On Thu, Mar 18, 2004 at 04:08:43PM -0500, Gregory (Grisha) Trubetskoy wrote:
> >
> > Is there a way to preserve the cq hash across reboots?
> >
> > I saw the script that someone e-mail that preserves the amount of space
> > available, but what about the hash itself?
> >
> > Otherwise it looks like if you delete any files that you created prior to
> > reboot you don't gain any space back.
>
> assumed that you ahve set up quota hashes properly,
> assigned a quota hash to the vserver context and
> activated quota with the quota tools (not required
> for per context disk limits) then thequota hashes
> write to the quota files on the partition (in the
> vserver root path), and are read by the quota system
> on quota start ...
>
> disk limits do not use the quota hashes themselves
> but they make use of the structures and require
> them to be assigned ... saving the 'current' value
> on vserver stop and restoring it on vserver start
> should be sufficient ...
>
> disk space is 'gained' for files/inodes belonging
> to the context (xid of the files) freeing them, you
> will not gain space for files in the host context
> when they are removed from within a vserver ...
>
> (use lsxid/chxid to manage the xids)
>
> > Or am I missing something?
>
> HTH,
> Herbert
>
> > Grisha
>
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver