Summary: | Remounting remaining filesystems readonly failed when started openvz ve | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | billy <shing6326> |
Component: | [OLD] Server | Assignee: | Peter Volkov (RETIRED) <pva> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | vserver-devs+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | lsof result |
Description
billy
2009-11-29 03:57:59 UTC
Why do you need to start networking from /etc/vz/conf/<vpsid>.start? It's possible to use vzctl to configure network. Ah, disregard previous message. Nevertheless, I'm unable to reproduce this problem. What happens without .start script? Show me vzctl output with --verbose enabled. What's in dmesg? Is problem reproducible with venet configuration? (In reply to comment #2) > Ah, disregard previous message. > > Nevertheless, I'm unable to reproduce this problem. What happens without .start > script? Show me vzctl output with --verbose enabled. What's in dmesg? Is > problem reproducible with venet configuration? > server cache # vzctl start 101 Starting container ... Mounted /usr/portage to /vz/root/101/usr/portage Container is mounted Setting CPU units: 1000 Configure meminfo: 65536 Set hostname: vz101gentoo Running container script: /etc/vz/dists/scripts/gentoo-set_hostname.sh Running container script: /etc/vz/dists/scripts/set_dns.sh File resolv.conf was modified Configure veth devices: veth101 Adding interface veth101 to bridge br0 on CT0 for CT101 Running container script: /etc/vz/conf/101.start Setting IP: 192.168.1.234 Setting Gateway: 192.168.1.4 Container start in progress... dmesg: [589971.990960] CT: 101: started [589972.293728] device veth101 entered promiscuous mode [589972.293837] br0: port 5(veth101) entering listening state [589987.288019] br0: port 5(veth101) entering learning state [590002.288016] br0: topology change detected, propagating [590002.288029] br0: port 5(veth101) entering forwarding state 101.conf: ONBOOT="yes" # UBC parameters (in form of barrier:limit) KMEMSIZE="11055923:11377049" LOCKEDPAGES="256:256" PRIVVMPAGES="65536:69632" SHMPAGES="21504:21504" NUMPROC="240:240" PHYSPAGES="0:2147483647" VMGUARPAGES="33792:2147483647" OOMGUARPAGES="26112:2147483647" NUMTCPSOCK="360:360" NUMFLOCK="188:206" NUMPTY="16:16" NUMSIGINFO="256:256" TCPSNDBUF="1720320:2703360" TCPRCVBUF="1720320:2703360" OTHERSOCKBUF="1126080:2097152" DGRAMRCVBUF="262144:262144" NUMOTHERSOCK="360:360" DCACHESIZE="3409920:3624960" NUMFILE="9312:9312" AVNUMPROC="180:180" NUMIPTENT="128:128" # Disk quota parameters (in form of softlimit:hardlimit) DISKSPACE="1048576:1153024" DISKINODES="200000:220000" QUOTATIME="0" # CPU fair sheduler parameter CPUUNITS="1000" VE_ROOT="/vz/root/$VEID" VE_PRIVATE="/vz/private/$VEID" OSTEMPLATE="gentoo-openvz-x86-2009.11.17" ORIGIN_SAMPLE="vps.basic" HOSTNAME="vz101gentoo" NAMESERVER="192.168.1.4" NETIF="ifname=eth0,bridge=br0,mac=00:18:51:A0:15:B4,host_ifname=veth101,host_mac=00:18:51:FA:52:42" UUID: ceb1fc67-c7f9-13a8-bb76-ed31acc00656 I tried to remove the HOSTNAME,NAMESERVER,NETIF and 101.start, problem still here, here is the startup message: gentoosrv cache # vzctl start 101 Starting container ... Mounted /usr/portage to /vz/root/101/usr/portage Container is mounted Setting CPU units: 1000 Configure meminfo: 65536 Container start in progress... Thanks, shing (In reply to comment #2) > Ah, disregard previous message. > > Nevertheless, I'm unable to reproduce this problem. What happens without .start > script? Show me vzctl output with --verbose enabled. What's in dmesg? Is > problem reproducible with venet configuration? > sorry here is the vps.mount, /etc/vz/conf/vps.mount #!/bin/bash # if one of these files does not exist then something is # really broken [ -f /etc/vz/vz.conf ] || exit 1 [ -f $VE_CONFFILE ] || exit 1 . /etc/vz/vz.conf . $VE_CONFFILE ISGENTOO=$(echo "$OSTEMPLATE" | grep ^gentoo) if [ $ISGENTOO ]; then mkdir -p $VE_ROOT/usr/portage mount -n --bind /usr/portage $VE_ROOT/usr/portage && echo "Mounted /usr/portage to $VE_ROOT/usr/portage" fi exit ${?} If I just start the vz service without starting any VE, the / umount successful, but when I start any VE template with any distro eg:gentoo,debian,centos downloaded from http://download.openvz.org/template/precreated/contrib/, the problem will appear. (In reply to comment #4) > here is the vps.mount What's the output of vzctl --verbose stop 101? And what's inside vps.umount (it's required to unmount everything there to make stop successful)? Created attachment 211641 [details]
lsof result
(In reply to comment #5) > (In reply to comment #4) > > here is the vps.mount > > What's the output of vzctl --verbose stop 101? And what's inside vps.umount > (it's required to unmount everything there to make stop successful)? > ok now i make it simpler, i try to remove all the start/stop/mount/umount scripts, here is the start and stop message: server conf # vzctl start 102 Starting container ... Container is mounted Setting CPU units: 1000 Configure meminfo: 131072 Container start in progress... server conf # vzctl stop 102 Stopping container ... Container was stopped Container is unmounted 102.conf ONBOOT="no" KMEMSIZE="11055923:11377049" LOCKEDPAGES="256:256" PRIVVMPAGES="131072:196608" SHMPAGES="21504:21504" NUMPROC="240:240" PHYSPAGES="0:2147483647" VMGUARPAGES="131072:2147483647" OOMGUARPAGES="131072:2147483647" NUMTCPSOCK="360:360" NUMFLOCK="188:206" NUMPTY="16:16" NUMSIGINFO="256:256" TCPSNDBUF="1720320:2703360" TCPRCVBUF="1720320:2703360" OTHERSOCKBUF="1126080:2097152" DGRAMRCVBUF="262144:262144" NUMOTHERSOCK="360:360" DCACHESIZE="3409920:3624960" NUMFILE="9312:9312" AVNUMPROC="180:180" NUMIPTENT="128:128" DISKSPACE="1048576:1153024" DISKINODES="200000:220000" QUOTATIME="0" CPUUNITS="1000" VE_ROOT="/vz/root/$VEID" VE_PRIVATE="/vz/private/$VEID" OSTEMPLATE="centos-5-i386-default-5.4-20091116" ORIGIN_SAMPLE="vps.basic" #UUID: 2206f5c6-36a6-63a4-0a60-8144a53ebd5c when I shutdown, still get an error, so I entered a root password and run umount -a, it shows: umount: /dev device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) umount: / device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) I attached the lsof result, hope that can give us some hints... Thanks, shing problem solved /etc/vz/vz.conf DISK_QUOTA=no (In reply to comment #8) > problem solved > /etc/vz/vz.conf > DISK_QUOTA=no Actually this is workaround but not fix. But well, I'm unable to reproduce this problem, so I'll close it until somebody provides hints how to reproduce or finds what causes this issue. |