Re: [vserver] creating a vserver on his own partition

ADNET Ghislain wrote:
>
>>
>> What util-vserver version and what error do you get? lost+found has
>> been ignored since 0.30.210, so unless you're running really ancient
>> utils or you actually have files in it, it should work fine...
>>
> here is the situation:
>
> vserver20:/usr/local/.aqadmin/home/aqadmin%(root)> mount
> /dev/md1 on / type ext3 (rw,noatime)
> tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> procbususb on /proc/bus/usb type usbfs (rw)
> tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
> none on /dev/shm type tmpfs (rw)
> /dev/md0 on /boot type ext2 (rw)
> */dev/mapper/volume1-root40265 on /vservers/vserver21 type ext3
> (rw,noatime)
> /dev/mapper/volume1-tmp40265 on /vservers/vserver21/tmp type ext3 (rw)
> /dev/mapper/volume1-var40265 on /vservers/vserver21/var type ext3 (rw)*
>
>
> vserver20:/usr/local/.aqadmin/home/aqadmin%(root)> vserver vserver21
> build -m debootstrap -n vserver21 --force --context 40265 --hostname

                                     ^^^
Don't use --force, especially if you're using a mount point.

> vserver21.aqserver.net --interface nodev:213.246.42.65/24 --interface
> 65=lo:127.0.0.65/24 -- -d etch --
> --exclude=dhcp-client,fdutils,ipchains,klogd,modutils,ppp,\
> pppconfig,pppoe,pppoeconf,pciutils,iptables,linux-kernel-log-daemon,klogd,sysklogd,makedev,ifupdown
> --include=nano,rsync,sudo,ruby,rdoc,libxml-ruby,libopenssl-ruby,lsb-release,vim,debian-archive-keyring,syslog-ng,tcsh
>
> /usr/local/etc/vservers/.defaults/vdirbase/vserver21/tmp

And this means you already have a tmp directory in there. If it's a
brand new filesystem, why would you?

> *mv: cannot move `/usr/local/etc/vservers/.defaults/vdirbase/vserver21'
> to `/usr/local/etc/vservers/.defaults/vdirbase/vserver21.~1191834135~':
> Device or resource busy*

So... If you do it right (i.e. on an actually empty filesystem) and
don't use --force, everything should be fine...

-- 
Daniel Hokka Zakrisson