Proxmox destoyed container

S

Sheh

New Member
Jul 12, 2011
4
0
1
I run migration of container on an other host. Bun disk space was ended on destination host. So now i see just half of my container on host destionation and absolutly nothing on sourse host.
Any suggestions?

Here is a part of /var/log/vzctl.log:
2011-07-11T20:56:28+0700 vzctl : CT 102245 : Stopping container ...
2011-07-11T20:56:30+0700 vzctl : CT 102245 : Container was stopped
2011-07-11T20:56:30+0700 vzctl : CT 102245 : Container is unmounted
2011-07-11T21:00:01+0700 venetclean : CT 102245 : CT died, clear IPs:
2011-07-11T21:20:08+0700 vzctl : CT 102245 : Destroying container private area: /var/lib/vz/private/102245
2011-07-11T21:20:09+0700 vzctl : CT 102245 : Container private area was destroyed

Just interesting, with which command Proxmox destroyed /var/lib/vz/private/102245? rm -rf?
 
Last edited:
Sheh said:
Just interesting, with which command Proxmox destroyed /var/lib/vz/private/102245? rm -rf?
Click to expand...

Just take a look at /usr/sbin/vzmigrate

Usually that script stops when it get errors from the filesystem. What filesystem do you use (did you change the default)?
 
OK, thanks for your reply :)

HTML: 
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/pve-root   17G  1.9G   15G  12% /
tmpfs                 7.9G     0  7.9G   0% /lib/init/rw
udev                   10M  916K  9.2M   9% /dev
tmpfs                 7.9G     0  7.9G   0% /dev/shm
/dev/cciss/c0d0p1     504M   31M  448M   7% /boot
/dev/mapper/virt-lvol0
                      237G  5.5G  219G   3% /var/lib/vz

cat /etc/fstab
HTML: 
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
UUID=8d359730-79f4-4db4-a9de-8d1802dbbad9 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
/dev/mapper/virt-lvol0 /var/lib/vz ext3 defaults 0 1
proc /proc proc defaults 0 0
, where /dev/mapper/virt-lvol0 - LUN on SAN
 
You must log in or register to reply here.
Top Bottom