You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2013/09/09 15:08:53 UTC

[jira] [Reopened] (CLOUDSTACK-3565) Restarting libvirtd service leading to destroy storage pool

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei Zhou reopened CLOUDSTACK-3565:
----------------------------------


Reopen it as it exists.

The libvirt pool is lost after restart libvirt but it is still mounted if there exist VMs running on the host.

(1) 
[root@cs-kvm012 ~]# virsh version
Compiled against library: libvirt 0.10.2
Using library: libvirt 0.10.2
Using API: QEMU 0.10.2
Running hypervisor: QEMU 0.12.1

[root@cs-kvm012 ~]# df |grep -v dev
Filesystem           1K-blocks      Used Available Use% Mounted on
192.168.103.1:/storage/da-upgr-01-primary
                     7811748864 1099777024 6711971840  15% /mnt/72301816-c94a-3ad4-a1fd-7a1749c56171

[root@cs-kvm012 ~]# [root@cs-kvm012 ~]# virsh pool-list;service libvirtd restart;virsh pool-list
Name                 State      Autostart
-----------------------------------------
72301816-c94a-3ad4-a1fd-7a1749c56171 active     no
a4824596-4587-4083-8d09-abca28f2d18f active     no

Stopping libvirtd daemon:                                  [  OK  ]
Starting libvirtd daemon:                                  [  OK  ]

Name                 State      Autostart
-----------------------------------------
a4824596-4587-4083-8d09-abca28f2d18f active     no
                                                           [  OK  ]
[root@cs-kvm012 ~]# df |grep -v dev
Filesystem           1K-blocks      Used Available Use% Mounted on
192.168.103.1:/storage/da-upgr-01-primary
                     7811748864 1099777024 6711971840  15% /mnt/72301816-c94a-3ad4-a1fd-7a1749c56171

[root@cs-kvm012 ~]# cat /proc/mounts  |grep mnt
192.168.103.1:/storage/da-upgr-01-primary /mnt/72301816-c94a-3ad4-a1fd-7a1749c56171 nfs4 rw,sync,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,noac,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.103.111,minorversion=0,local_lock=none,addr=192.168.103.1 0 0



(2) 

root@cs-kvm003:~# virsh version
Compiled against library: libvir 0.9.13
Using library: libvir 0.9.13
Using API: QEMU 0.9.13
Running hypervisor: QEMU 1.2.0

root@cs-kvm003:~# df |grep mnt
172.16.5.30:/storage/cs-105-primary 7811748864 1099777024 6711971840  15% /mnt/c7e524e3-5861-3001-bf5a-b304e55892d8

root@cs-kvm003:~# virsh pool-list
Name                 State      Autostart
-----------------------------------------
c7e524e3-5861-3001-bf5a-b304e55892d8 active     no
f53e7a7b-eb65-4b94-a559-40569d39ab39 active     no

root@cs-kvm003:~# virsh pool-list;service libvirt-bin restart;virsh pool-list
Name                 State      Autostart
-----------------------------------------
c7e524e3-5861-3001-bf5a-b304e55892d8 active     no
f53e7a7b-eb65-4b94-a559-40569d39ab39 active     no

libvirt-bin stop/waiting
libvirt-bin start/running, process 3321
Name                 State      Autostart
-----------------------------------------

root@cs-kvm003:~#  df |grep mnt
172.16.5.30:/storage/cs-105-primary 7811748864 1099777024 6711971840  15% /mnt/c7e524e3-5861-3001-bf5a-b304e55892d8



                
> Restarting libvirtd service leading to destroy storage pool
> -----------------------------------------------------------
>
>                 Key: CLOUDSTACK-3565
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3565
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.2.0
>         Environment: KVM 
> Branch 4.2
>            Reporter: Rayees Namathponnan
>            Assignee: Rajesh Battala
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> Steps to reproduce
> Step 1 : Create cloudstack step in kvm
> Step 2 : From kvm host check "virsh pool-list"
> Step 3:  Stop and start libvirtd service 
> Step 4 : Check "virsh pool-list"
> Actual Result 
> "virsh pool-list"  is blank after restart libvird service 
> [root@Rack2Host12 agent]# virsh pool-list
> Name                 State      Autostart
> -----------------------------------------
> 41b632b5-40b3-3024-a38b-ea259c72579f active     no
> 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active     no
> fff90cb5-06dd-33b3-8815-d78c08ca01d9 active     no
> [root@Rack2Host12 agent]# service cloudstack-agent stop
> Stopping Cloud Agent:
> [root@Rack2Host12 agent]# virsh pool-list
> Name                 State      Autostart
> -----------------------------------------
> 41b632b5-40b3-3024-a38b-ea259c72579f active     no
> 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active     no
> fff90cb5-06dd-33b3-8815-d78c08ca01d9 active     no
> [root@Rack2Host12 agent]# virsh list
>  Id    Name                           State
> ----------------------------------------------------
> [root@Rack2Host12 agent]# service libvirtd stop
> Stopping libvirtd daemon:                                  [  OK  ]
> [root@Rack2Host12 agent]# service libvirtd start
> Starting libvirtd daemon:                                  [  OK  ]
> [root@Rack2Host12 agent]# virsh pool-list
> Name                 State      Autostart
> -----------------------------------------

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira