similar to: About using LVM

Trying to setup a volume group with puppet lvm and this:- volume_group { "my_vg": ensure => present, physical_volumes => "/dev/sdb /dev/sdc /dev/sdd", require => [ Physical_volume["/dev/sdb"], Physical_volume["/dev/sdc"], Physical_volume["/dev/sdd"] ] } Fails with this in the debug

First run of puppet performs a configsync and an attempt to load the downloaded plugins, the provider fails to be found by puppet in this first run, another re-run of puppet is needed for the provider to work, see debug output below. Is this a bug or am I missing something you think? The error in short: err: /Stage[main]/Ibe::Slave/Logical_volume[mysql]: Could not evaluate: No ability to

Hello, Using the LVM module/providers from the forge I want to create a logical volume at the maximum size and I cannot work out how to do this. physical_volume -> volume_group -> logical_volume -> filesystem -> mount All works fine but you have to hard code the size for the logical volume. Anyone know if this is possible ? Thanks Paul -- You received this message because you

I can''t work this out and I''m getting frustrated. :( Puppet is complaining: err: Failed to apply catalog: Could not find dependency Lvm::Volume_group[bcvg] for Lvm::Application_volume[cache] at /truth/sauce/env/prod/modules/object_store/manifests/server.pp:47 Yet, if I comment out that line so that puppet runs ok, and then look at the state.yml file on the client, I see:

Hello, I have this bit of code that tries to remove a physical volume from the VG (which consists of /dev/sda5 amd /dev/sdb1): volume_group { "system": ensure => absent, physical_volumes => "/dev/sdb1", } But I get this error: Error: Execution of

On 05/21/18 11:07 PM, Mike Burger wrote: > On 2018-05-21 4:33 pm, Miguel Gonzalez wrote: >> Hi, >> >> ? I am searching around and I can?t find any GUI LVM manager included in >> a Centos live CD. >> >> ? I am trying to resize a LVM partition in a Centos 6.9 machine with a >> live CD. >> >> ? If I need any other distro, It?s fine with me

On 2018-05-21 4:33 pm, Miguel Gonzalez wrote: > Hi, > > ? I am searching around and I can?t find any GUI LVM manager included > in > a Centos live CD. > > ? I am trying to resize a LVM partition in a Centos 6.9 machine with a > live CD. > > ? If I need any other distro, It?s fine with me > > ? Thanks! > > ? Miguel I make no promises that it is

Hi, ? I am searching around and I can?t find any GUI LVM manager included in a Centos live CD. ? I am trying to resize a LVM partition in a Centos 6.9 machine with a live CD. ? If I need any other distro, It?s fine with me ? Thanks! ? Miguel ?

I've written some %pre code to grab a few files off a logical volume, if it exits, before the disk gets formatted, but can't get get it to work correctly. Essentially: %pre ... lvm vgscan lvm vgchange -a y ... if [ -d /dev/vol0 ]; then # do stuff fi lvm vgremove -f vol0 The problem is that /dev/vol0 does not exist after lvm vgchange. I added a few debug statements (lvm pvdisplay, lvm

On 10/11/2017 12:20 PM, ML wrote: > Hi everyone, > > I've read on the gluster & redhat documentation, that it seems > recommended to use XFS over LVM before creating & using gluster volumes. > > Sources : > https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/Formatting_and_Mounting_Bricks.html > >

Volumes are aggregation of bricks, so I would consider bricks as a unique entity here rather than volumes. Taking the constraints from the blog [1]. * All bricks should be carved out from an independent thinly provisioned logical volume (LV). In other words, no two brick should share a common LV. More details about thin provisioning and thin provisioned snapshot can be found here. * This thinly

On 10/11/2017 09:50 AM, ML wrote: > Hi everyone, > > I've read on the gluster & redhat documentation, that it seems recommended to > use XFS over LVM before creating & using gluster volumes. > > Sources : > https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/Formatting_and_Mounting_Bricks.html > >

After some extra reading about LVM snapshots & Gluster, I think I can conclude it may be a bad idea to use it on big storage bricks. I understood that the LVM maximum metadata, used to store the snapshots data, is about 16GB. So if I have a brick with a volume arount 10TB (for example), daily snapshots, files changing ~100GB : the LVM snapshot is useless. LVM's snapshots doesn't

Thanks Rafi, that's understood now :) I'm considering to deploy gluster on a 4 x 40 TB? bricks, do you think it would better to make 1 LVM partition for each Volume I need or to make one Big LVM partition and start multiple volumes on it ? We'll store mostly big files (videos) on this environement. Le 11/10/2017 ? 09:34, Mohammed Rafi K C a ?crit?: > > On 10/11/2017 12:20

Hi All, I'm having issue with creating LVM volume via libvirt. XML of LVM StoragePool is:     VG01             /dev/VG01       (existing vg) XML of create volume in lvm pool is:     ub_test01.img     0     1                 When I create the volume with above XML defn, lvs command to list logical volume shows a value in the origin column indicating it was created as snapshot.. the

Hello, I'm currently setting up a virtualization infrastructure based on CentOS 5.4 x86_64 and KVM. I want to use LVM because of its flexibility, especially the ability to add more disk space to a guest if needed. We are considering using an hardware RAID1 with BBU as the lowest layer. My question is: where is it recommended to put the LVM? 1. On the host only In that case, the guests

On 06/23/2015 10:54 AM, Marko Vojinovic wrote: > (1) I have no valid usecase for it. I don't remember when was the last > time I needed to resize partitions (probably back when I was trying to > install Windows 95). Disk space is very cheap, and if I really need to > have *that* much data on a single partition, another drive and a few > intelligently placed symlinks are usually

Hi all, I'm not sure if this is the right place to ask, but it's worth a shot. I have installed CentOS 6.5 on one of our servers, and have just installed SolusVM. I have also set up LVM, with a PV on /dev/sda4 (which is GPT formatted, and 3.12TB is size). The problem I'm having is that when I create the VG, it will not show up under /dev/<VG-name>, which it's supposed to

On 6/23/2015 11:23 AM, Mauricio Tavares wrote: > AIX does use lvm a lot. Main difference is their filesystem > allows live shrinking. Kinda nice to dynamically size a partition > depending on needs, as opposite to the so often suggested approach of > formatting the entire drive as one single partition. Symlinking is > great until whatever the destination is does not mount. I

Hi! Folowing setup: 4x HD 500TB 1st: /boot 4GB, remaining part LVM 2nd, 3rd, 4th all LVM LVM volumes: - 30G /root - 8G /var - 8G /tmp - 200G /var/log/pgsql - 800G /var/spacewalk - 4G swap System boots into emergency mode because it does not find any of the logical volumes defined, because it does not enable the LVM volume group. Giving "lvm", then "vgchange -a y",