On Mon, Jul 07, 2003 at 04:29:24PM +0200, Lars Braeuer wrote:
ok, it seems to work now. after working on the same user the whole time, I added a new one while quota was turned on. all the stats (blocks, inodes) seem to be update fine now and even the user can view his quotas with "quota". I think I'm going to reinstall my test vserver and see if it works from the start now.
also any new usernames are reported as id with a leading "#" by repquota but not as the acutal username. I hope this is the right behaviour?
a simple explanation should clarify that: (see http://www.13thfloor.at/VServer/Concepts.shtml)
I already tried to understand this. ;)
quota tools try to resolve (hide) the numeric values the quota system actually uses (can be supressed with
the -n option) but as the context specific versions
of for example 'root' will have some offset (2^16 * ctx)
they won't be found in the host (physical) server.
although they should be shown correctly in the virtual server, otherwise something _is_ wrong ...
well, in repquota I'm only getting the numbers instead of the actual usernames of the newly added users. but "quota" shows the right names and quota seems to work fine with the users in the vserver.
User used soft hard grace used soft hard grace ---------------------------------------------------------------------- root -- 88926 0 0 6503 0 0 daemon -- 2 0 0 3 0 0 man -- 1 0 0 1 0 0 mail -- 7 0 0 6 0 0 news -- 1 0 0 1 0 0 #262144 -- 21957 0 0 1536 0 0 #196608 -- 55 0 0 0 0 0 #263145 -- 11 100 200 6 0 0 #263146 -- 1 155 255 3 0 0 #327680 -- 1 0 0 0 0 0 #263147 -- 5 10 20 4 30 40 #262152 -- 25 0 0 9 0 0 #262150 -- 122 0 0 15 0 0
I didn't lock the vserver to a single security context before (using S_CONTEXT). maybe you should mention this in your how-to for other people reading it?
you are absolutely right, I will add this to the how-to ...
after locking the vserver to a context id quotas were properly saved even after restarting the vserver.
so you can ignore *most* of my last mail:
let me know if something is unclear
the following line is added by the vquota patch, is this some kind of debugging message?
printk("ext3_new_inode: context = %d\n", inode->i_context);
I installed the patch yesterday on an ext3 system for the first time. it flooded all of my shells with this message: ext3_new_inode: context = 0
probably everytime a new inode is created?
I removed the message from the patch. is this line of any importance besides debugging?
