From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Sun 06 Jul 2003 - 23:45:13 BST
On Mon, Jul 07, 2003 at 12:20:49AM +0200, Lars Braeuer wrote:
> ok, thanks a lot. turning on the quota from within the vserver is now
> working, after adding CAP_QUOTACTL to the conf.
>
> now there's another problem. am I just too stupid or is it a bug? ;)
> I ran quotacheck within the vserver and set the quota for a user.
>
> Filesystem blocks soft hard inodes soft hard
> /dev/hdv1 41 10 500 10 0 0
>
> after turning the quota on with "quotaon -auvg" in the vserver, edquota for
> that user looks like this:
>
> Filesystem blocks soft hard inodes soft hard
> /dev/hdv1 0 0 0 0 0 0
>
> at the same time "repquota -auvg" shows the following for that user:
> quota_user +- 41 10 500 5days 10 0 0
>
> turning off the quota with "quotaoff -auvg" brings back the old values in
> edquota, just like before quota was turned on in the vserver.
>
> any idea?
jepp!
the current linux quota solution (not only vquota ;)
is a hybrid kernel/user space solution, where information
is passed over different channels ...
- filesystem (the quota files)
- quotactl on the device
if you have quota turned off, for example, information
can only be exchanged over the filesystem, which, if no
sync is done later on, can result in a copletely different
view, from the kernel side ...
the hopefully correct sequence should be:
- mount filesystem with quota options
- perform quotacheck (probably forced to overwrite)
- turn on quota (from now on kernel should be in sync with files)
- edit quota values for any user
- check with repquota
- check with dd (hard way *G*)
everything, except for the mount, should be done from
'inside' the virtual server ...
> my hostsystem setup:
> linux-2.4.20-ctx17
> vquota patch
> quota-tools-3.08
> vquota-tools-0.12
hmm, why not 2.4.21? are there any reasons?
> within the vserver:
> quota-tools 3.04 debian package
> also tested quota-tools 3.08
the older quota tools had some issues with
edquota understanding the 'new' quota format,
you should at least use 3.07 ...
HTH,
Herbert
> lars
>
> Herbert Poetzl wrote:
> >On Sun, Jul 06, 2003 at 12:31:40AM +0200, Lars Braeuer wrote:
> >
> >>hi herbert,
> >
> >
> >Hi Lars!
> >
> >
> >>I setup a vserver on an LVM partition with vquota using your how-to
> >>located at:
> >>http://www.13thfloor.at/VServer/HowTo_LVMQS.shtml
> >>
> >>everything works fine, until it comes to the point where I want to
> >>activate the quota in the vserver issuing "quotaon -avug". I get the
> >>following message:
> >>
> >>quotaon: using //aquota.user on /dev/hdv1 [/]: Operation not permitted
> >
> >
> >you will ned CAP_QUOTACTL to do this from inside the
> >server ...
> >
> >
> >>- vserver lvm partition is mounted to /vservers/LV01
> >>- vrsetup is run from LV01.sh (just like in the how-to)
> >>- quotacheck -avug is run on startup
> >>
> >>is there another way to activate quota in the vserver, i.e. from the
> >>hostsystem?
> >
> >
> >this is always possible from the host system, because
> >if you use the vroot only (not the vquota) patch, the
> >quota system doesn't change and in the other case
> >it isn't important from where quota was enabled ...
> >
> >HTH,
> >Herbert