similar to: puppet-lvm and volume group issues

i would like to use the module puppet-lvm and would like to pass values to it. I have it setup properly as a module but I can''t for the lfe of me get it to take any values that I put in my baseconfig.pp in my home folder. like shouldn''t something like this work?? puppet-lvm {''setvolume'': vg => ''myvg'', pv =>

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

I''ve installed the puppet labs lvm module. After fixing the missing "}" at line 20 in init.pp (really?!?!), I''m getting this:'' err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type physical_volume at /truth/sauce/env/prod/modules/role/manifests/common.pp:43

How can I pass an array to a define? It''s not documented in the puppet language guide. I''ve got: define lvm::create_vg ( $pvdisks ) { exec { ''pvcreate'': command => "/sbin/pvcreate -yf $pvdisks", unless => "/sbin/pvdisplay $pvdisks", ... } } class someclass { lvm::create_vg {

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

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

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:

> > From: Scott Robbins <scottro11 at gmail.com> > Date: May 06, 2016 12:32:55 PM > To: CentOS mailing list <centos at centos.org> > Subject: Re: [CentOS] resize lvm > > On Fri, May 06, 2016 at 06:19:35PM +0000, Wes James wrote: > > I have a laptop that I put centos 7 on and I started out with a 30gig partition. I resized the other part of the disk to allow

Hi all, I had centos 5.9 installed with one of its volumes (non-root) on LVM: ... /dev/vgapps/lvapps /opt/apps ext3 defaults 1 2 ... Then installed centos 6.4 on this servers but without exporting this volume (I wanted to reuse it). After that instead importing it I did: # pvcreate /dev/sddlmac # vgcreate vgapps /dev/sddlmac And then realised that I should have

'--no-degraded' flag in the first mdadm call inhibits the startup of array unless all expected drives are present. This will prevent starting arrays in degraded state. Second mdadm call (after LVM is scanned) will scan unused yet devices and make an attempt to run all found arrays even they are in degraded state. Two new tests are added. This fixes rhbz1527852. Here is boot-benchmark

Can anybody tell me if it makes a difference if domU''s have separate LVM volume groups? For instance, the Xen User Manual ( http://tx.downloads.xensource.com/downloads/docs/user/#SECTION03330000000000000000) says, when setting up a domU''s disks with LVM, to do a vgcreate vg /dev/sda10 Should each domU have it''s own volume group, or can all the domU''s share

Hi All, I''ve downloaded a Puppet module and I''m trying to add a parameter to it by editing lib/puppet/type/<resource>.rb. I simply added: newproperty(:pcfree) do desc "My description here" end In the corresponding file in lib/puppet/provider, I do something with :pcfree. Whenever I call the resource from Puppet with my new parameter, it keeps

Hello, I have a physical volume with no volume group. # /sbin/pvscan -n WARNING: only considering physical volumes in no volume group PV /dev/sdg2 lvm2 [148.95 GB] Total: 1 [148.95 GB] / in use: 0 [0 ] / in no VG: 1 [148.95 GB] Can I just create a volume group -- for example: # vgcreate my_volume_group /dev/sdg2 and then activate it: # vgchange -a y my_volume_group I

Hi guys, sorry if this is trivial, but I have been googling a couple days and already compromised a test disk trying to figure this out, so I thought it is time to ask for some advice. I have a disk that comes from a clean and working CentOS4.2 install, and I am trying to use an external usb to ide converter to mount it on another workstation with CentOS4.2. I am trying this to better

I'm testing doing kickstart installations on Xen VMs. This is the first time I'm trying out kickstart at all, so I rather think I'm doing something wrong in the kickstart configuration than it is a Xen issue. I use a modified kickstart file from an earlier manual installation with a very basic filesystem setup. It fails with "SystemError: vgcreate failed for VolGroup00".

Hi, I recently installed centos for the first time and I like it! Also, I just started working with lvm. The following warnings are genertated whenever I run one of lvm commands on the external usb disk (MyBook by Western Digital). * What could be the source for those messages? * Should I worry about them (writing into the created LV's seems to work)? * If yes, how to fix them? [root

Hi, I'm trying to set up an iscsi 12.5 TB storage for some data backup. Doing so, I had some difficulties to find the right tool, maybe it's also a question of the system settings... The server is a 32Bit CentOS 5.3 with the recent updates. Ths iscsi connection can be establised. fdisk and parted fail to create any information on the device or fail completely. using the lvm tools

Add the 'label' optional argument to the mkfs action, so it is possible to set a filesystem label direct when creating it. There may be filesystems not supporting changing the label of existing filesystems but only setting it at creation time, so this new optarg will help. Implement it for the most common filesystems (ext*, fat, ntfs, btrfs, xfs), giving an error for all the others, just

On 05/06/2016 02:15 PM, Wes James wrote: > I found this: > > # lvextend -l +100%FREE /dev/myvg/testlv > > doing a search. What's the difference between 100%VG and 100%FREE? For the special case of "100%" there is no difference. For values less than 100% with a non-empty VG, the two are quite different, e.g., (50% of VG) != (50% of the free space in VG). -- Bob

Use findfs LABEL=ABC and mount LABEL=ABC instead. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 29 ++++++++++++++++------------- scripts/ovirt-config-storage | 2 -- scripts/ovirt-functions | 18 ++++++++++-------- 3 files changed, 26 insertions(+), 23 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index