libvirt-users is a better list, and I noticed that Gareth already posted on it and got some replies.

Sharad Mishra
Open Virtualization
Linux Technology Center
IBM

Inactive hide details for Chip Vincent ---08/17/2011 10:06:54 PM---Perhaps we should put this on libvirt-list@redhat.com?Chip Vincent ---08/17/2011 10:06:54 PM---Perhaps we should put this on libvirt-list@redhat.com?

          Chip Vincent <cvincent@linux.vnet.ibm.com>
          Sent by: libvirt-cim-bounces@redhat.com

          08/17/11 10:05 PM
          Please respond to
          cvincent@linux.vnet.ibm.com; Please respond to
          List for discussion and development of libvirt CIM <libvirt-cim@redhat.com>


To

libvirt-cim@redhat.com

cc


Subject

Re: [Libvirt-cim] which vols added to storage pool during refresh?

Perhaps we should put this on libvirt-list@redhat.com?

On 08/17/2011 12:46 PM, Gareth S Bestor wrote:
>
> We're looking at a problem when we have a libvirt pool defined, below
>
> [root@xnl2192 ~]# virsh pool-dumpxml ScsiPool-host2
> <pool type='scsi'>
> <name>ScsiPool-host2</name>
> <uuid>f2ea1882-881f-9f49-838d-39e070f68002</uuid>
> <capacity>136583315456</capacity>
> <allocation>136583315456</allocation>
> <available>0</available>
> <source>
> <adapter name='host2'/>
> </source>
> <target>
> <path>/dev/disk/by-id</path>
> <permissions>
> <mode>0700</mode>
> <owner>-1</owner>
> <group>-1</group>
> </permissions>
> </target>
> </pool>
>
> As you can see, this pool maps to /dev/disk/by-id. There may be a large
> number of actual volume entries in /dev/disk/by-id, however it appears
> only a distinct subset of them are actually added into the libvirt pool
> when you do a pool-refresh. What does libvirt check when determining
> which, and whether or not, to add one of these volume into the vol-list?
>
> In particular, we have a case when one specific volume in
> /dev/disk/by-id is *not* added into the pool, and no amount of
> pool-refresh makes a difference. We did notice that if you remove all
> the sym links in /dev/disk/by-id and do a pool-refresh, that libvirt
> re-scans the bus, recreates the links in /dev/disk/by-id, and adds (some
> of) the volumes back into the vol-list. But not this one problematic
> vol, so clearly there is something about this vol that libvirt doesnt
> like and why it is (deliberately?) not added to the pool.
>
> What checks, etc does libvirt make against vols when determining whether
> to add them to a pool?
>
> - G
>
> Dr. Gareth S. Bestor
> IBM Senior Software Engineer
> Systems & Technology Group - Systems Management Standards
> 971-285-6375 (mobile)
> bestor@us.ibm.com
>
>
>
> _______________________________________________
> Libvirt-cim mailing list
> Libvirt-cim@redhat.com
>
https://www.redhat.com/mailman/listinfo/libvirt-cim

--
Chip Vincent
Open Virtualization
IBM Linux Technology Center
cvincent@linux.vnet.ibm.com

_______________________________________________
Libvirt-cim mailing list
Libvirt-cim@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-cim