search for: pvcreate

...ll, 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 import it instead of pvcreate/vgcreate. Can I restore previous state and data from this volume ? I have files from /etc/lvm/backup (taken before reinstallation) with its old definition. Regards P.

...t again. Instead of taking my J4400 ( 24 x 1T disks) and making a big RAID60 out of it which Linux cannot make a filesystem on, I'm created 4 x RAID6 which each are 3.64T I then do : sfdisk /dev/sd{b,c,d,e} <<EOF ,,8e EOF to make a big LVM partition on each one. But then when I do : pvcreate /dev/sd{b,c,d,e}1 and then pvdisplay It shows each one as only half its actual size. But if I take the last one and wipe the partition table and just do pvcreate on the entire disk, it works pvcreate /dev/sde And then if I take the results from that and use the size to force a size on another...

...size partition labeled as Linux Raid Autodetect and created the first r6 array w/ mdadm. I normally create and mark partitions as raid or lvm so people know what's going on. The first md array is obviously too large for fdisk and parted doesn't create lvm partitions does it? Should I just pvcreate the raw /dev/md0 and not worry about creating an lvm partition on it, or should/(can?) I? Thanks! jlc

Hello, I am preparing a brick as LVM thin volume for a test slave node using this documentation: https://docs.gluster.org/en/main/Administrator-Guide/formatting-and-mounting-bricks/ but I am confused regarding the right "--dataalignment" option to be used for pvcreate. The documentation mentions the following under point 1: "Create a physical volume(PV) by using the pvcreate command. For example: pvcreate --dataalignment 128K /dev/sdb Here, /dev/sdb is a storage device. Use the correct dataalignment option based on your device. Note: The device name...

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 { ''bcvg01'': pvdisks => [''/dev/xvdb1'',...

...otonmail.ch> wrote: Hello, I am preparing a brick as LVM thin volume for a test slave node using this documentation:? https://docs.gluster.org/en/main/Administrator-Guide/formatting-and-mounting-bricks/ but I am confused regarding the right "--dataalignment" option to be used for pvcreate. The documentation mentions the following under point 1: "Create a physical volume(PV) by using the pvcreate command. For example: pvcreate --dataalignment 128K /dev/sdb Here, /dev/sdb is a storage device. Use the correct dataalignment option based on your device. ? ? Note: The device name...

[This email is either empty or too large to be displayed at this time]

...I am preparing a brick as LVM thin volume for a test slave node using this documentation: >> >> https://docs.gluster.org/en/main/Administrator-Guide/formatting-and-mounting-bricks/ >> >> but I am confused regarding the right "--dataalignment" option to be used for pvcreate. The documentation mentions the following under point 1: >> >> "Create a physical volume(PV) by using the pvcreate command. For example: >> >> pvcreate --dataalignment 128K /dev/sdb >> >> Here, /dev/sdb is a storage device. Use the correct dataalignment opti...

...exit $status +} +trap cleanup INT QUIT TERM EXIT + +guestfish <<EOF +# Add 2 empty disks +sparse $disk1 100M +sparse $disk2 100M +run + +# Create a raid1 based on the 2 disks +md-create test "/dev/sda /dev/sdb" level:raid1 + +# Create volume group and logical volume on md device +pvcreate /dev/md127 +vgcreate vg0 /dev/md127 +lvcreate-free lv0 vg0 100 +EOF + +# Ensure list-md-devices now returns the newly created md device +output=$( +guestfish --format=raw -a $disk1 --format=raw -a $disk2 <<EOF +run +list-md-devices +lvs +EOF +) + +expected="/dev/md127 +/dev/vg0/lv0"...

I now how to expand a LVM by creating a new drive as described here: http://lists.centos.org/pipermail/centos/2007-February/032664.html, the steps are: # pvcreate /dev/sda3 # vgextend VolGroup00 /dev/sda3 Now, I want to know how to expand a LVM without create /dev/sda3? Suppose I have 2 GB free (unpartitioned) and LVM use /dev/sda2 (8 GB). How to make /dev/sda2 become 10 GB? Then resize LVM to 10 GB. Regards, Wendy ___________________________________...

...rray. Now I have to find a way to tell LVM about the extra space. It seems there are two ways: 1. delete partition with fdisk and recreate a larger one. This is obviously a bit tricky if you do not want to lose data, I haven't investigated further yet. 2. create another partition on the disk, pvcreate another pv and then add it to the existing volume group with vgextend 3. a possible third way: increase the partition size. According to Google most if not all disk tools want to resize a file system as well and since there is no file system they will fail. I'm not sure about the status with...

Hi, I've got a DAS DELL MD1000 with a bunch of SATA drives in RAID 5 configuration with total space of 5.4TB. This box is attached to a CentOS5 system (kernel 2.6.18-53.1.6.el5). Any idea how to make this space usable? Is there a limit how big a partition can be? What is the work around? Is there a limit how big a file system ca be? I've tried to partition it but no matter how bug

...newer one for my home lan usage. The disk layout on the older one is a 2 partition (/boot and /) with / being a logical volume. Laying out what I think I need to do looks like this : 1. yank old drive and cable up to newer system, expecting this 2nd drive to now be /dev/sdb on the new box 2. pvcreate /dev/sdb1 3. vgextend VolGroup00 /dev/sdb1 (VolGroup00 is the volume group name on both system, pretty much default installs in both cases) 3. lvextend -l+100% /dev/VolGroup00 4. resize2fs / The disk in the old system looks like : [root at cow ~]# fdisk -l /dev/hda Disk /dev/hda: 122.9 GB, 12294...

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 more space for centos.? I then created an unformated partition in the available space,? ran pvcreate /dev/sda4 vgextend lvname /dev/sda4 lvextend -L 184.46G /dev/lvname/root but when I run: sudo resize2fs /dev/lvname/root I get: resize2fs: Bad magic number in super-block while trying to open /dev/lvname/root Couldn't find valid filesystem superblock. How do I resize the volum...

...any distro but I hope someone can answer it anyway. I took the following steps but was puzzled by the outcome of the test at the end: 1. Create a RAID1 array called md3 with two 750GB drives 2. Create a RAID1 array called md9 with two 500GB drives 3. Initialise md3 then md9 as physical volumes (pvcreate) 4. Create a new volume group called "3ware" with md3 (helps me remember what controller the disks are on) 5. Use vgextend and add md9 to the 3ware volume group. 6. Add a logical volume filling the volume group then create a ext3 filesystem on the entire volume. Now I started moving...

...impact of destroying a running pool is on running VMs. Does taking the pool off-line cause any issues with running VMs or is the only affect that the pool is unavailable for management by libvirt? These are the commands that I ran to create my pool and expand it after a kickstart of the server: pvcreate -ff -y /dev/mapper/mpath? virsh pool-define-as --name GuestVols --type logical --source-dev /dev/mapper/mpatha --target /dev/GuestVols virsh pool-build GuestVols virsh pool-start GuestVols virsh pool-autostart GuestVols virsh pool-destroy --pool GuestVols vgextend GuestVols /dev/mapper/mpath{b..d}...

...have sufficient extents to move the > data off of this disk. If you have another disk then you could try > adding it to the VG and then moving the extents. > > | 2. Replacing the broken PV: > | > | I was able to create a new PV and restore the VG Config/meta data: > | > | # pvcreate --restorefile ... --uuid ... /dev/sdc1 > | # vgcfgrestore --file ... vg_hosting > | > | However, vgchange would give this error: > | > | # vgchange -a y > | device-mapper: resume ioctl on failed: Invalid argument > | Unable to resume vg_hosting-lv_home (253:4) > |...

...for database , webserver, and appserver), we're see a great improvement in managability and performance (>10%) by just dropping LVM, and most partitions. In your example, the resize process is 7 functional steps: 1. Increase size of VMDK 2. In VM OS, Create Partition (??) 3. REBOOT (!!) 4. PVCreate 5. VGExtend 6. LVExtend 7. Resize2fs Going to a LVM/partition-less setup reduces expansion to 3 steps and we don't need to take the VM OS offline! 1. Increase size of VMDK 2- Inside the VM, OS, rescan the scsi drive with:'echo 1 >/sys/class/scsi_device//rescan; dmesg' (dmesg will ch...

...with the following: 1. Removing the broken PV: # vgreduce --force vg_hosting /dev/sdc1 Physical volume "/dev/sdc1" still in use # pvmove /dev/sdc1 No extents available for allocation 2. Replacing the broken PV: I was able to create a new PV and restore the VG Config/meta data: # pvcreate --restorefile ... --uuid ... /dev/sdc1 # vgcfgrestore --file ... vg_hosting However, vgchange would give this error: # vgchange -a y device-mapper: resume ioctl on failed: Invalid argument Unable to resume vg_hosting-lv_home (253:4) 0 logical volume(s) in volume group "vg_hosting&q...

On 2/27/2015 4:37 PM, James A. Peltier wrote: > | I was able to create a new PV and restore the VG Config/meta data: > | > | # pvcreate --restorefile ... --uuid ... /dev/sdc1 > | oh, that step means you won't be able to recover ANY of the data that was formerly on that PV. -- john r pierce 37N 122W somewhere on the middle of the left coast