similar to: LVM Thin Volumes & Storage Pools

On 09/08/2013 10:19 PM, Osier Yang wrote: > Could you paste the bug number? https://bugzilla.redhat.com/show_bug.cgi?id=924672 -- Jorge

On 09/09/2013 02:42 AM, Osier Yang wrote: > And we have the bug to support the thin pool, sorry you won't be able > to use it until the bug is fixed. Could you share the bug number so I can follow it? Thanks, Jorge

On 09/09/13 03:53, Jorge Fábregas wrote: > Hi, > > Is it possible to create a storage pool based on an LVM thin pool? I > read a recent bugzilla but the problem there was that the storage-pool > became unusable AFTER creating a thinpool which is a different case. Could you paste the bug number? > > Thanks, > Jorge > >

On 09/09/13 11:14, Jorge Fábregas wrote: > On 09/08/2013 10:19 PM, Osier Yang wrote: >> Could you paste the bug number? > https://bugzilla.redhat.com/show_bug.cgi?id=924672 > > The error pasted by Cole in the bug should be the real reason, which is overridden by the later pool stopping. And we have the bug to support the thin pool, sorry you won't be able to use it until

Hello, as usual, I'm few years behind trends so I have learned about LVM thin volumes recently and I especially like that your volumes can be "sparse" - that you can have 1TB thin volume on 250GB VG/thin pool. Is it somehow possible to use that with libvirt? I have found this post from 2014: https://www.redhat.com/archives/libvirt-users/2014-August/msg00010.html which says

Please don't use lvm thin for vm. In our hosting in Russia we have 100-150 vps on each node with lvm thin pool on ssd and have locks, slowdowns and other bad things because of COW. After we switching to qcow2 files on plain ssd ext4 fs and happy =). 2017-11-04 23:21 GMT+03:00 Jan Hutař <jhutar@redhat.com>: > Hello, > as usual, I'm few years behind trends so I have learned

Do you have some comparasion of IO performance on thin pool vs. qcow2 file on fs? In my case each VM would have its own thin volume. I just want to overcommit disk-space. Regards, Jan On 2017-11-07 13:16 +0300, Vasiliy Tolstov wrote: >Please don't use lvm thin for vm. In our hosting in Russia we have >100-150 vps on each node with lvm thin pool on ssd and have locks, >slowdowns

Hi, I've changed the "default" storage-pool from "directory-based" to a "pre-formatted block-device" since my /var/lib/libvirt/images is on a partition of its own. I would like to use the "discard" option as well as other (noatime etc) on this filesystem. Is there a way to specify mount options in the storage-pool XML definition? Thanks, Jorge p.d.

Hi, I just installed a CentOS 6.5 System with the intention of using thinly provisioned snapshots. I created the volume group, a thinpool and then a logical volume. All of that works fine but when I create a snapshot "mysnap" then the snapshot volume gets displayed in the "lvs" output with the correct information but apparently no device nodes are created under

Hi, I've noticed huge write amplification problem with thinly provisioned logical volumes and I wondered if anyone can explain why it happens and if and how can be fixed. The behavior is the same on Centos 6.8 and Centos 7.2. I have a NVME card (Intel DC P3600 -2 TB) on which I create a thinly provisioned logical volume: pvcreate /dev/nvme0n1 vgcreate vgg /dev/nvme0n1 lvcreate

In the past, I've used LVM on MD RAID, and I'd like to try using LVM RAID in order to also add dm-integrity data to some LVs.? I've added new PVs to my VG, and I've converted some of my LVs to raid1 types, but I also have one thin pool that I use for VMs with multiple layers of snapshots.? That pool can't be converted, directly: # lvconvert --type raid1 -m 1

Hi All I'm trying to setup my LVM thin pool to support discards so that the pool can reclaim space even if the underlying device doesn't support trim. It is my understanding that all thin pools should support trim even if the underlying device doesn't. (please correct me if I'm wrong here) I have one centos server that does support trim and everything is working correctly but any

On Fri, Jun 26, 2015 at 10:51 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: >> , or alternatively making the LVs >> redundant after install is a single command (each) and you can choose >> whether it should be mere mirroring or some MD manged RAID level (modulo >> the LVM RAID MD monitoring issue). > > > I hadn't realized that. That's an

My guess? The passthrough is causing the error when the command passes through to the actual device, which doesn't support Trim. I don't know how it actually works, but you can try to poke it with this stick: copy a large file to this LV. Check the LV with lvdisplay. Delete the file. Fstrim. Lvdisplay. Now compare the two lvdisplay results. It should show the PEs used are less after

hi, how do i list storage pools and volumes using the python bindings? basically the python api calls for?virsh pool-list and virsh vol-list thanks

I still get the "the discard operation is not supported" fstrim error when the LVs are set to "nopassdown" Seems that when I use ext4 the fstrim reports that it worked but the LVs Data% does not decrease after the fstrim. xfs just throws the error. I've also been looking at the output of lsblk -D # lsblk -D NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO xvdb

Hello everyone, We're currently working with using libvirt as an abstract API to make our dealings with other hypervisors far easier and faster, however, we have our own storage API that connects/disconnects and makes LUNs available over iSCSI with iSER. We would have loved to use a storage pool however our system implements a one target per LUN/VDI, therefore, we'd have to create a pool

hi, i am trying to create a domain using libvirt 0.9.4 python api and i can't find any information on how to use the libvirt python api with linux logical volumes http://libvirt.org/guide/html-single/#Application_Development_Guide-Device_Config-Disks is TBD i figured out that i need to use defineXML to create a domain, however for the disk part in the xml, i am not sure if i need to create

On Tue, 01 Oct 2013 06:10:46 -0600 Eric Blake <eblake@redhat.com> wrote: > On 10/01/2013 06:04 AM, James Gibbon wrote: > > > > > > Hello all, > > > > I have a KVM guest VM which is a clone of a production machine > > running on a different physical server, incarnated from an > > image backup. > > Careful. You need to scrub more than

Hi, I'm trying to create a kickstart file that uses a thinly provisioned lvm volume as root but I've run into trouble. I installed a System manually using this option and this is the anaconda file produced: part /boot --fstype="xfs" --ondisk=vda --size=500 part pv.10 --fstype="lvmpv" --ondisk=vda --size=7691 volgroup centos_centos7 --pesize=4096 pv.10 logvol