On Tue, Sep 09, 2003 at 02:26:25PM +0200, Stephan Sachse wrote: > Hi, > > i try out the per Context Quota and do the following steps. > > * vanilla kernel 2.4.22 with alle patches from Herbert > * vserver-0.23 > > after reboot i setup the vroot with "vrsetup /dev/vroot/0 /dev/hda3" > (must i do that after every reboot??) > > hda3 is mounted on /mnt/vserversa and alle vServer are linked to > /vservers. A second hd is mounted on /dec/vserversb. > > now i use this command "chcontext --ctx 100 cqhadd -v /dev/hda3" to > activate the quota for vServer "v01" and start the vServer "v01" > > "quotacheck -avgu" and "quotaon -avgu" all works fine. > > now i setup a second vserver "v02" with the same userids and do the same > things for v02. Quota works fine ;) > > I make some test an got many crashes (i make a Photo from that ;)) when
hmm, sounds interesting, what crashes did you observe? > i do the "chcontext --ctx 100 cqhadd -v /dev/hda3" after i start the > vServer. Now i must wroth a script that adds the quota before the > vServer starts. But the Problem is the /dev/real/block/device. How can i > find out die real block device like /dev/hda3 for a vServer on demand > when the vServer starts. well, if you know, you use /dev/hda3 for _all_ vservers, it would always be /dev/hda3 and further, you would only require _one_ vroot device, so setting up the vroot on boot time, and just using /dev/vroot/0 for each server would be sufficient, wouldn't it? HTH, Herbert > cya later > /stephan > > -- > "Communication with an engineer is only slightly more difficult than > communication with the dead." -Lorren 'Rus' Stiles, Sr.
