search for: vgextend

Hi, I am trying to figure it out the best way to add a disk/partition to an existing LVM pool. A google search led me to this link (a thread from this same mailing list, September 2013): https://www.redhat.com/archives/libvirt-users/2013-September/msg00136.html The interesting part is this: " On 21/09/13 02:15, McEvoy, James wrote: I looked around but could not find any info on

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 _______________________________________________ Xen-user...

...ems 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 this for the tools that come with CentOS (fdisk, parted, other?) No....

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 volume? Thanks, -wes

...: 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 a lot of data onto the volume and iostat said all the data was being written to md9. Why that array? How does it decide which physi...

...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} vgdisplay GuestVols virsh pool-start --pool GuestVols virsh pool-info --pool GuestVols Is this the best way to create a managed pool across 4 LUNs? And to potentially expand the storage group in the future if more storage is needed? --jim

...e , 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 check that you...

...k space for root and home. My (successful) test procedure in a virtual environment looks like this: 1. devide /dev/sdb into /dev/sdb1 for root and /dev/sdb2 for home using parted 2. Convert disk to physical volume: pvcreate /dev/sdb1 3. add physical volume to volume group (called centos): vgextend centos /dev/sdb1 4. Allocate physical volume to a logical volume:lvextend -l +100$FREE /dev/centos/root 5. resize2fs /dev/centos/root or xfs_grows /dev/centos/root depending on file system used 6. repeat steps 2-6 for /home and sdb2 The mentioned instruction I've got from this...

...--------- now adding /dev/sdc to pool centos fails with: [root at hotelcaw ~]# ssm add -p centos /dev/sdc Device /dev/sdc not found (or ignored by filtering). Unable to add physical volume '/dev/sdc' to volume group 'centos'. SSM Error (2012): ERROR running command: "lvm vgextend centos /dev/sdc" I did a format 0 on the hard drive that makes up /dev/sdc with: dd if=/dev/zero of=/dev/sdc bs=8M I suspect I need to prepare it further before it can be added. Can anyone advise me on this issue? Many Thanks J.

Hi, This is my current config: /dev/md0 -> 200 MB -> sda1 + sdd1 -> /boot /dev/md1 -> 36 GB -> sda2 + sdd2 -> form VolGroup00 with md2 /dev/md2 -> 18 GB -> sdb1 + sde1 -> form VolGroup00 with md1 sda,sdd -> 36 GB 10k SCSI HDDs sdb,sde -> 18 GB 10k SCSI HDDs I have added 2 36 GB 10K SCSI drives in it, they are detected as sdc and sdf. What should I do if I

...speed of database access might improve. I use local LVM for my virtual disks with DRBD on top to mirror the disk to a backup server. If I change grub.conf to increase RAM disk size and increase host RAM, I could create a 35G RAM disk. I'd modify rc.local to add pvcreate /dev/ramdisk vgextend vg /dev/ramdisk lvconvert -m 1 --corelog vg/lv_database /dev/ramdisk Even with lv_database being 35G, it doesn't take long to activate the mirror. I haven't decided where to put the commands to turn off the lvm mirror. lvconvert -m 0 vg/lv_database vgreduce vg /dev/ramdisk pvremov...

...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, 122942324736 bytes 255 head...

...nts you're giving have to do with VMs. > Do you have some for straight-on-the-server, non-VM cases? I've used LVM on servers with hot-swap drives to migrate to new storage without downtime a number of times. Add new drives to the system, configure RAID (software or hardware), pvcreate, vgextend, pvmove, vgreduce, and pvremove (and maybe a lvextend and resize2fs/xfs_growfs). Never unmounted a filesystem, just some extra disk I/O. Even in cases where I had to shutdown or reboot a server to get drives added, moving data could take a long downtime, but with LVM I can live-migrate from place...

Hi all! I've got a VM at work running C6 on HyperV (no, its not my fault, that's what the company uses. I'd rather gag myself than own one of th ose things.) I ran out of disk space in the VM, so the admin enlarged the virtual disk. but now I realize I don't know how to enlarge the partition and its filesystem. I'll be googling, but in case I miss it, it'd be great if

...mplicity is desired. As a perk, your source LV becomes your backup. Procedure B ~~~~~~~~~~~ 1. Create backup LV with geometry identical to source LV geometry 2. Stop guest. 3. Create snapshot of source LV 4. Start guest 5. dd from snapshot of source LV to backup LV 6. Drop snapshot of source LV 7. vgextend source VG with additional PV 7. pvmove source LV to additional PV (opt) 8. vgsplit [source VG into additional VG with additional PV] (opt) 9. Modify guest configuration [to point to source LV on additional VG] Procedure B can be different for Linux guests in that, depending upon your guest filesys...

...cal LVM for my virtual disks with DRBD on top to mirror the > disk to a backup server. > > If I change grub.conf to increase RAM disk size and increase host RAM, > I could create a 35G RAM disk. > > I'd modify rc.local to add > pvcreate /dev/ramdisk > vgextend vg /dev/ramdisk > lvconvert -m 1 --corelog vg/lv_database /dev/ramdisk > > Even with lv_database being 35G, it doesn't take long to activate the > mirror. > > I haven't decided where to put the commands to turn off the lvm > mirror. > lvconvert -m...

...es 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 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 I find it easiest to do lvextend -l 100%VG /dev/lvname/rootI find it easiest to do lvextend -l 100%VG /dev/lvname/root. (Then, if practical, and since it's a laptop, I'm guessing it's not a production machi...

...rote: > > 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 > > > > I find it easiest to do lvextend -l 100%VG /dev/lvname/rootI find it > easiest to do lvextend -l 100%VG /dev/lvname/root. > (Then, if practical, and since it's a laptop, I'm guessing it&...

Hi, I added additional storage to my domU using xm block-attach and tap:aio. Then increased my root device (using vgextend, lvextend and resizefs) which is / or /dev/mapper/VolGroup00-LogVol00. Everything worked fine util I did "xm save domid test1.img" This stopped my domU. And now when I run: xm create domU -c , I am seeing -- Scanning logical volumes Reading all physical volumes. This may take a while...

I have a database server that is running out of space. All my databases are being stored in a 80G /opt partition. Because I'm using LVM, wouldn't I be able to pop the HDDs (a h/w raid volume) in, add it to the LVM, and resize my ext3 /opt partition? Everything that I've been reading says this is possible, but I'm not sure. Has anyone done this and are there any pitfalls to