Herbert,

Thanks a lot for your answer, you have been very kind and helpfull.

So this probably means, that doing a copy of a vserver running to make a new one, is not a good idea at all.

regards,

At 03:57 PM 4/25/2004, Herbert Poetzl wrote:
On Sun, Apr 25, 2004 at 12:25:10PM -0400, Jean-Christophe Petit wrote:
>
> Hello,
>
> I resolve the problem by doing a tar.gz of the whole vserver. Erase the
> vserver then Untar
> And then, It starts without a problem!
>
> is this a normal behavior ?

yes, it is ;)

best,
Herbert

> best regards,
> JC
>
> At 10:57 AM 4/25/2004, Herbert Poetzl wrote:
> >On Sat, Apr 24, 2004 at 07:51:42PM -0400, Jean-Christophe Petit wrote:
> >> Hello,
> >>
> >> I have a problem with "per context disk quota"
> >> I setup 5 vservers, and everything work very well.
> >> But, for the 6th and above: impossible to start them. I have the
> >following
> >> error :
> >> Can't execute /etc/rc.d/rc (Permission denied)
> >
> >this looks like the files in that vserver already
> >have a context tag (xid) which is unequal to the
> >xid of your server, hence permission denied.
> >
> >solutions: change the files in that vserver to
> >the xid of the vserver, or change them back to
> >the 'host' context (which can be done by touching
> >them from the hosts, for example)
> >
> >> I have kernel 2.4.25 with vs1.26 / quota 0.13 patch
> >
> >some things where added/fixed in vs1.27 - qh0.14
> >(probably not related to y<our issues, though)
> >
> >> The kernel was compiled with:
> >> Virtual Root device support
> >> (UID32/GID32) Persistent Context ID for files
> >
> >hope you are with ext2 or ext3, otherwise this
> >isn't the best choice ...
> >
> >> Quota support
> >>
> >> here is my mserver6 start up script. In the mserver6.conf, I use the
> >> context 6000
> >> (for all mserver : [n]000 context for mserver[n])
> >>
> >> #!/bin/sh
> >> case $1 in
> >> pre-start)
> >>         rm -f /vservers/mserver6/dev/hdv1
> >>         vrsetup /dev/vroot/0 /dev/hda4
> >
> >again, if you ahve more than one vserver, it
> >might not be such a good idea to put the vrsetup
> >here, as a shutdown of vserver N will 'delete'
> >the vroot config, and each 'second' startup
> >will fail at setting up the 'same' vroot device
> >
> >rule: one vroot device for each 'real' partition
> >
> >>         cp -fa /dev/vroot/0 /vservers/mserver6/dev/hdv1
> >>         /usr/src/cq-tools-0.06/cqhadd -v -x 5000 /dev/vroot/0
> >>         /usr/src/cq-tools-0.06/cqdlim -x 5000 -S 0,0,`du -skx
> >> /vservers/mserver6 |awk '{print $1}'`,40000000,10 -v /dev/vroot/0 &
> >>         ;;
> >> post-start)
> >>         ;;
> >> pre-stop)
> >>         ;;
> >> post-stop)
> >>         /usr/src/cq-tools-0.06/cqhrem -x 5000 /dev/vroot/0
> >>         vrsetup -d /dev/vroot/0 /dev/hda4
> >>         ;;
> >> *)
> >>         echo $0 pre-start
> >>         echo $0 pre-stop
> >>         echo $0 post-start
> >>         echo $0 post-stop
> >>         ;;
> >> esac
> >>
> >> thanks for your answers,
> >
> >HTH,
> >Herbert
> >
> >> best regards,
> >> Jesse
> >>
> >>
> >> _______________________________________________
> >> Vserver mailing list
> >> [EMAIL PROTECTED]
> >> http://list.linux-vserver.org/mailman/listinfo/vserver
>
>
> _______________________________________________
> Vserver mailing list
> [EMAIL PROTECTED]
> http://list.linux-vserver.org/mailman/listinfo/vserver


_______________________________________________
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to