Cloud virtuozzo6.X ploop container tidak dapat di started atau mounted atau Unmount,
kita cek dulu yang bermasalah adalah CTID 3760884
[root@cubot5 ~]# vzlist -a CTID NPROC STATUS IP_ADDR HOSTNAME 1 3 running 192.168.44.37 - 3760884 - mounted 192.168.0.135 node1.carauntuk.com 5964519 - stopped 10.0.0.20 cpanel-centos6.carauntuk.com
coba kita start containernya bisa atau tidak? ternyata gagal dengan pesan “Failed to umount”, kali ini kita dapatnya ploop yang gagal di umount padahal status dari containernya mounted
[root@cubot5 ~]# vzctl start 3760884 Unmount image: /vz/private/3760884/root.hdd Failed to umount image: Error in do_umount (ploop.c:1007): Failed to umount /vz/root/3760884: Device or resource busy [22] Container is already mounted Starting the Container ... Setting permissions 20002 dev 0x7d00 dumpe2fs 1.41.12 (17-May-2010) Setting mount options for image=/vz/private/3760884/hostxdisk.img opts=1 balloon_ino=12,pfcache_csum,pfcache=/vz/pfcache Setting permissions for image=/vz/private/3760884/hostxdisk.img Adding IP addresses: 192.168.0.135 192.168.0.111/255.255.255.0 Hostname of the Container set: node1.carauntuk.com File resolv.conf was modified Setting permissions 60010 dev 0xa430b6e1 Turn userquota on quotaon: using //aquota.group on /dev/ploop42046p1 [/]: Device or resource busy quotaon: using //aquota.user on /dev/ploop42046p1 [/]: Device or resource busy Failed to turn quota on Failed to setup 2nd level quota Unmount image: /vz/private/3760884/root.hdd Failed to umount image: Error in do_umount (ploop.c:1007): Failed to umount /vz/root/3760884: Device or resource busy [22] Failed to start the Container
kita coba umount ya, apa error atau tidak karena kan statusnya tadi mounted? gagal juga
[root@cubot5 ~]# vzctl umount 3760884 Unmount image: /vz/private/3760884/root.hdd Failed to umount image: Error in do_umount (ploop.c:1007): Failed to umount /vz/root/3760884: Device or resource busy [22]
selanjutnya kita cek prosesnya apa ada atau tidak? ternyata ada proses e4defrag, dan lain2, karena servernya juga mati jadi proses ini kita abaikan dulu saja
[root@cubot5 ~]# lsof 2>/dev/null | grep 3760884 e4defrag 717861 root 13r DIR 182,672737 4096 2 /vz/root/3760884 e4defrag 717861 root 15r DIR 182,672737 4096 131073 /vz/root/3760884/var e4defrag 717861 root 16r DIR 182,672737 4096 131730 /vz/root/3760884/var/spool e4defrag 717861 root 17r DIR 182,672737 4096 273257 /vz/root/3760884/var/spool/exim e4defrag 717861 root 18r DIR 182,672737 4096 529681 /vz/root/3760884/var/spool/exim/input e4defrag 717861 root 19r DIR 182,672737 65536 55968964 /vz/root/3760884/var/spool/exim/input/n bash 725150 root cwd DIR 0,21 0 63986 /pstorage/mcs1/private/3760884
coba kita pastikan yang ada di proc CTID tadi mengunakan ploop apa? dengan cara
[root@cubot5 ~]# grep 3760884 /proc/mounts /dev/ploop42046p1 /vz/root/3760884 ext4 rw,relatime,barrier=1,data=ordered,balloon_ino=12,pfcache_csum,pfcache=/vz/pfcache,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0
ok kita dapat tergetnya dan bersiap untuk kita umount dengan cara yang berbeda, bukan dari CTIDnya melainkan langsung ploop, sepertinya berhasil di umount, karena yang masalah tadi di awal adalah umount ini,
[root@cubot5 ~]# ploop umount -d /dev/ploop42046p1 Unmounting file system at /vz/root/3760884 Unmounting device /dev/ploop42046 Opening delta /pstorage/mcs1/private/3760884/root.hdd/root.hds
sekarang kita coba start containernya, dan ternyata gagal, dengan pesan mount? ini error baru
[root@cubot5 ~]# vzctl start 3760884 Mount image: /vz/private/3760884/root.hdd Mount image: /vz/private/3760884/hostxdisk.img Failed to mount image /vz/private/3760884/hostxdisk.img: Error in ploop_mount_image (ploop.c:1935): Image /pstorage/mcs1/private/3760884/hostxdisk.img/root.hds already used by device /dev/ploop63896 Failed to mount image: Error in ploop_mount_image (ploop.c:1935): Image /pstorage/mcs1/private/3760884/hostxdisk.img/root.hds already used by device /dev/ploop63896 [152] Unmount image: /vz/private/3760884/root.hdd Unmount image: /vz/private/3760884/hostxdisk.img
kita coba mount, apakah berhasil? iya berhasil tanpa error
[root@cubot5 ~]# vzctl mount 3760884 Mount image: /vz/private/3760884/root.hdd Mount image: /vz/private/3760884/hostxdisk.img Container is mounted
kita ulangi start lagi, apakah bisa? yap prosesnya mulus dari umount sampai mount dan starting container
[root@cubot5 ~]# vzctl start 3760884 Unmount image: /vz/private/3760884/root.hdd Unmount image: /vz/private/3760884/hostxdisk.img Container is unmounted Mount image: /vz/private/3760884/root.hdd Mount image: /vz/private/3760884/hostxdisk.img Container is mounted Starting the Container ... Setting permissions 20002 dev 0x7d00 dumpe2fs 1.41.12 (17-May-2010) Setting mount options for image=/vz/private/3760884/hostxdisk.img opts=1 balloon_ino=12,pfcache_csum,pfcache=/vz/pfcache Setting permissions for image=/vz/private/3760884/hostxdisk.img Adding IP addresses: 192.168.0.135 192.168.0.111/255.255.255.0 Hostname of the Container set: node1.carauntuk.com File resolv.conf was modified Setting permissions 60010 dev 0x2b40b6f1 Turn userquota on Starting the Container ...
kita cek statusnya running sekarang
[root@cubot5 ~]# vzlist -a CTID NPROC STATUS IP_ADDR HOSTNAME 1 3 running 192.168.44.37 - 3760884 144 running 192.168.0.135 node1.carauntuk.com 5964519 - stopped 10.0.0.20 cpanel-centos6.carauntuk.com
dan kita coba ping ipnya dan berhasil artinya server sudah kembali UP
[root@cubot5 ~]# ping 192.168.0.135 PING 192.168.0.135 (192.168.0.135) 56(84) bytes of data. 64 bytes from 192.168.0.135: icmp_seq=1 ttl=64 time=0.049 ms 64 bytes from 192.168.0.135: icmp_seq=2 ttl=64 time=0.034 ms ^C --- 192.168.0.135 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1944ms rtt min/avg/max/mdev = 0.034/0.041/0.049/0.009 ms
kita cek datanya dengan konsole ke containernya, untuk memastikan apakah ada partisi yang tidak termount atau hilang? ternyata tidak
[root@cubot5 ~]# vzctl enter 3760884 entered into Container 3760884 CT-3760884-bash-4.1# df -h Filesystem Size Used Avail Use% Mounted on /dev/ploop11087p1 5.5T 2.5T 2.8T 48% / none 9.0G 8.0K 9.0G 1% /dev none 9.0G 0 9.0G 0% /dev/shm /dev/ploop15521p1 6.3T 5.4T 905G 86% /backup
hati – hati anda login sebagai root@ pada system server apa yang anda lakukan tidak dapat di roleback, pastikan selalu backup settingan.
** use at your own risk**