From: Gregory (Grisha) Trubetskoy (grisha_at_ispol.com)
Date: Thu 18 Mar 2004 - 23:10:57 GMT
On Thu, 18 Mar 2004, Herbert Poetzl wrote:
> saving the 'current' value on vserver stop and restoring it on vserver
> start should be sufficient ...
I guess I'm confused as to whether mounting the filesystem with tagctx is
sufficient. I'm on 1.26 (so I don't have lsxid), and I was following
instructions from:
http://vserver.13thfloor.at/Linux2.6/index.php?page=Per+Context+Disk+Limits
(I'm not interested in quotas, I'm only interested in per-context disk
limits.)
OR I'm not properly restoring the limits. Here is what I do:
# mount | grep hda2
/dev/hda2 on /vservers type ext3 (rw,tagctx)
... no I create a file from within the vserver 10187. after this:
# /usr/local/cq-tools-0.06/cqdlim -x 10187 -v /dev/hda2
inodes: 160/50000
blocks: 21004/1073741 (5%)
... now lets unmount and remount /vservers
# umount /vservers
# mount /vservers
# /usr/local/cq-tools-0.06/cqdlim -x 10187 -v /dev/hda2
dlimctl failed: No such device or address
... this is ok I suppose, now try to restore them
# /usr/local/cq-tools-0.06/cqdlim -x 10187 -S 0,50000,21004,1073741,5 -v /dev/hda2
dlimctl failed: No such device or address
... is this right? let's try again:
# /usr/local/cq-tools-0.06/cqhadd -x 10187 -v /dev/hda2
adding quota hash for /dev/hda2 ... succeeded.
# /usr/local/cq-tools-0.06/cqdlim -x 10187 -S 160,50000,21004,1073741,5 -v /dev/hda2
inodes: 160/50000
blocks: 21004/1073741 (5%)
... but now if I delete the file created inside vserver before all this,
it doesn't affect the number of blocks used. I'm guessing it's because
cqhadd just wiped everything out, but without it cqdlim doesn't work.
Or should I just ignore those instructions and follow the ones on
http://vserver.13thfloor.at/Linux2.6/index.php?page=Per+Context+Quota
Thanks Herbert for all your help, BTW!
Grisha
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver