[libvirt] [PATCH v3 4/4] logical: Display thin lv's found in a libvirt managed volume group

Pavel Hrdina phrdina at redhat.com
Tue Feb 2 13:30:08 UTC 2016

On Tue, Feb 02, 2016 at 09:11:51AM +0100, Ján Tomko wrote:
> On Mon, Feb 01, 2016 at 03:29:53PM -0500, John Ferlan wrote:
> > Modify the regex for the 'devices' (a/k/a 'extents') from "(\\S+)"
> > (e.g., 1 or more) to "(\\S*)" (e.g., zero or more).
> > 
> > Then for any "thin" lv's found, mark the volume as a sparse volume so
> > that the volume wipe algorithm doesn't work.
> > 
> > Since a "thin" segtype has no devices, this will result in any "thin"
> > lv part of some thin-pool within a volume group used as a libvirt pool
> > to be displayed as a possible volume to use.
> > 
> A thin pool is another layer on top of some of the LVs in the VG.
> I think it deserves a separate pool type.

I must agree with Jan, and also already wrote the same for v2 patch.  The thin
pool and thin LV shouldn't be mixed with normal logical pool even they share the
same VG.


More information about the libvir-list mailing list