On Tue, May 18, 2004 at 04:46:26PM +0900, Dan Keimatsu wrote: > > At Tue, 18 May 2004 08:08:54 +0200, > Herbert Poetzl wrote: > > > > On Tue, May 18, 2004 at 02:03:34PM +0900, [EMAIL PROTECTED] wrote: > > > > > > Sorry for the late response. > > > > > > At Tue, 11 May 2004 13:25:43 +0200, > > > Herbert Poetzl wrote: > > > > > > > > On Tue, May 11, 2004 at 08:03:58PM +0900, Dan Keimatsu wrote: > > > > > > > > > > To activate quota function within security context, > > > > > we refered to "http://www.13thfloor.at/old/VServer/HowTo_LVMQ.shtml";, > > > > > and built our own system. As a result, testing command "quotacheck" > > > > > and "repquota" on the system works fine. > > > > > > > > I assume 'on the system' referrs to the host? > > > > > > yes. > > > > > > > > However, when we used "edquota" command to set quota for a user as a > > > > > root, the user could create a file which exceeds over quota. > > > > > > > > > > At this time, the result of "repquota" was like this. > > > > > > > > > > "user +- 2052 1024 1024 6days 7 0 0" > > > > > > > > > > Also, the results of "quotaon" or " quotaoff" were below, and error > > > > > messages were returned. > > > > > > > > > > #quotaoff / > > > > > quotaoff: quotactl on /dev/hdv1 [/]: No such device or address > > > > > quotaoff: quotactl on /dev/hdv1 [/]: No such device or address > > > > > > > > > > #quotaon / > > > > > quotaoff: quotactl on /dev/hdv1 [/]: No such device or address > > > > > quotaoff: quotactl on /dev/hdv1 [/]: No such device or address > > > > > > > > which was almost expected ... the docu is just > > > > outdated, a community member started to update > > > > the quota documentation, but was lost in action ... > > > > > > OK. > > > > > > > > Could someone tell me how quota works right, please. > > > > > > > > the best docu atm can be found at the documentation > > > > section on linux-vserver.org, here is a link to the > > > > quota part: > > > > > > > > http://vserver.13thfloor.at/Linux2.6/index.php?page=Per+Context+Quota > > > > > > > > basically you have to add a quota hash for each > > > > (part,xid) tuple and use the vroot device to proxy > > > > quotaioctls in a secure way to the kernel ... > > > > > > > > > I tried to do what it says, but it did not work right. > > > > > > What did not work right is the following; > > > > > > 1:Using mount comannd with "tagctx" Option ends up with "bad option" > > > > depending on the branch it is tagxid or tagctx but > > I'd guess you didn't patch the quota patches at all ... > > I am sorry for the lack of important information. > > > please provide the following infos: > > > - kernel version > > 2.4.26 > > > - patches applied > > patch-2.4.26-vs1.27.diff > patch-2.4.25-vs1.27-q0.14.diff
sounds good so far ... hmm, which file tagging (xid) did you select with the kernel config? did you enable quota? which filesystem do you use? > > - usespace tools > > cq-tools-0.06.tar > vr-tools-0.14.tar.bz2 > > > > 2:executing "cqhadd -v -x 100 /dev/vroot/0" ends up with > > > "adding quota hash for/dev/vroot/0 ... failed: Invalid argument" > > > > > > Since these two things did not work right,I could not move to the next > > > step. > > > > > > Now,I build to vserver with LVM. > > > each vserver has own partition. > > > > > > then i want to give a separate quota space per vserver. > > > > for this you 'just' need to make use of the vroot > > device ... > > yes. > I finished executing commands "mknod /dev/vroot/0 b 4 0". > and vservser.sh which is > pre-start) > e2fsck -p /dev/Volume00/LogVol01 > mount -o rw,usrquota,grpquota /dev/Volume00/LogVol01 /vservers/vs1 > rm -f /vservers/vs1/dev/hdv1 > vrsetup /dev/vroot/0 /dev/Volume00/LogVol01 > cp -fa /dev/vroot/0 /vservers/vs1/dev/hdv1 > ;; okay, just make sure, that you use a different vroot device for each lvm partition best, Herbert > > > --pertitions-- > > > df -h > > > /dev/hda3 494M 77M 392M 17% / > > > /dev/hda1 251M 13M 226M 6% /boot > > > /dev/hda5 3.7G 2.0G 1.6G 56% /home > > > none 189M 0 189M 0% /dev/shm > > > /dev/hda2 4.0G 764M 3.0G 20% /usr > > > /dev/Volume00/LogVol01 7.9G 532M 7.2G 7% /vservers/vs1 > > > /dev/Volume00/LogVol02 7.9G 532M 7.2G 7% /vservers/vs2 > > > /dev/Volume00/LogVol03 7.9G 532M 7.2G 7% /vservers/vs3 > > > --------------- > > > > > > please,give me an advice. > > > > > > > HTH, > > > > Herbert > > > > > > > > PS: is this linux-vserver in Japan? > > > > > > right now this technology is not well-known, but since it is a grate > > > technology,I think more and more peaple would depend on it. > > > > best, > > Herbert > > > > > > > Thanks in advance. > > > > > > > > > > --- > > > > > Dan Keimatsu > > > > > _______________________________________________ > > > > > Vserver mailing list > > > > > [EMAIL PROTECTED] > > > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > > > > > > > --- > > > Dan Keimatsu > > > > -- > Dan Keimatsu _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
