search for: pvresize

Hi, I'm needing to expand a LUN on my EMC CX4-120 SAN. (Well I already had done it). On this LUN I had a PV of a cLVM VG. Know I need to run pvresize on it. Has anybody done this on a cLVM PV ? I'm trying to rescan the devices, but I can't "see" the new size. And, googling on it I can only find RHEL5.2 responses. Thanks in advance, Antonio. -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...

LVM2 >= 2.02.171 requires the ‘--yes’ option to force pvresize to work in various circumstances, eg. reducing the size of an existing PV. Pass this flag unconditionally. Note this does NOT break earlier versions which just ignore this flag. --- daemon/lvm.c | 1 + 1 file changed, 1 insertion(+) diff --git a/daemon/lvm.c b/daemon/lvm.c index c186a5a5e..6c57...

Hello, I have a CentOS VM with only one disk on a Xenserver. The disk has 2 partitions: /dev/xvda1 -> /boot /dev/xvda2 -> a physical volume for LVM I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I just have to do "pvresize /dev/xvda" to have the additional space added to the disk. But for some reason it does not work for this disk. [root ~]# pvresize /dev/xvda Failed to find physical volume "/dev/xvda". 0 physical volume(s) resized / 0 physical volume(s) not resized [root ~]# pvresize /dev/xvda2...

...e disk on a Xenserver. > > > > The disk has 2 partitions: > > > > /dev/xvda1 -> /boot > > /dev/xvda2 -> a physical volume for LVM > > > > > > I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I > > just have to do "pvresize /dev/xvda" to have the additional space added > to > > the disk. But for some reason it does not work for this disk. > > > > [root ~]# pvresize /dev/xvda > > Failed to find physical volume "/dev/xvda". > > 0 physical volume(s) resized / 0 physical...

What's the easiest way to transition to a larger HD when using LVM2? I'm running Centos 4.4. I'm going from a 20gb HD to a 40gb HD. I've already DD'd it to the 40gb HD. So now I have 20gb of unused space. Ideally, I'd like to make it one big physical space for the logical space instead of making another physical partition to expand the logical. Here is what I have now

...artition on my HD and just add it to my Volume Group and extend my Volume Group, however, given that it would be two contiguous partitions on the HD, I was just wondering if there was a way of resizing the original partition within the VG without causing any problems. I tried looking at tools like pvresize but I can't seem to understand the right arguments to use it as whatever I try never seems to resize the original partition itself. I also looked at system-config-lvm GUI tool, but that doesn't seem to allow me to make the PV any larger. Does anyone have any suggestions? Thanks! Eric

...size change: * hdparm -z /dev/sdb * partx -a -v /dev/sdb * partprobe -s * echo "1" > /sys/block/sdb/device/rescan And while dmesg reported that it recognized the partition change, LVM did still not see it. So eventually, I was still forced to reboot, after which everything (pvresize, lvresize, resize2fs) worked fine. Environment: * A VMWare virtual machine * CentOS 6.7 (Final) Is there any other way I'm missing? Is this caused by the fact that I was trying to resize a partition that is under the root file system? If so, then is it really impossible to do it live?...

Hi, this small patch series exposes one of the utility in f2fs-tools, and use it to expand f2fs partitions in virt-resize. Thanks, Pino Toscano (2): New API: f2fs_expand resize: expand f2fs partitions daemon/Makefile.am | 1 + daemon/f2fs.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++ generator/actions_core.ml | 9 +++++++++ generator/proc_nr.ml | 1 +

.../dev/sdb Disk /dev/sdb: 438.4 GB, 438489317376 bytes 255 heads, 63 sectors/track, 53309 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 35539 285466986 8e Linux LVM When i run "pvresize /dev/sdb1" the output tells me it has been resized, but actually the physical volume didn't expand to the partition size 438GB. [root at srv1 ~]# pvresize /dev/sdb1 Physical volume "/dev/sdb1" changed 1 physical volume(s) resized / 0 physical volume(s) not resized [root...

...resize/virt-resize.pod | 10 ++++++++-- 2 files changed, 18 insertions(+), 4 deletions(-) diff --git a/resize/resize.ml b/resize/resize.ml index 1a21e4dff..8e4bb1b16 100644 --- a/resize/resize.ml +++ b/resize/resize.ml @@ -136,7 +136,7 @@ let debug_logvol lv = type expand_content_method = | PVResize | Resize2fs | NTFSResize | BtrfsFilesystemResize | XFSGrowFS - | Mkswap + | Mkswap | ResizeF2fs let string_of_expand_content_method = function | PVResize -> s_"pvresize" @@ -145,6 +145,7 @@ let string_of_expand_content_method = function | BtrfsFilesystemResize -> s_"...

...ENV{RESIZE}=="1", \ ENV{ID_FS_TYPE}=="ext[3-4]", \ RUN+="/sbin/resize2fs /dev/%k" ACTION=="change", KERNEL=="vd*", \ ENV{RESIZE}=="1", \ ENV{ID_FS_TYPE}=="LVM2_member", \ RUN+="/sbin/pvresize /dev/%k" Signed-off-by: Milos Vyletel <milos.vyletel at sde.cz> --- drivers/block/virtio_blk.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index 8ad21a2..5990382 100644 --- a/drivers/block/virtio_blk...

...ENV{RESIZE}=="1", \ ENV{ID_FS_TYPE}=="ext[3-4]", \ RUN+="/sbin/resize2fs /dev/%k" ACTION=="change", KERNEL=="vd*", \ ENV{RESIZE}=="1", \ ENV{ID_FS_TYPE}=="LVM2_member", \ RUN+="/sbin/pvresize /dev/%k" Signed-off-by: Milos Vyletel <milos.vyletel at sde.cz> --- drivers/block/virtio_blk.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index 8ad21a2..5990382 100644 --- a/drivers/block/virtio_blk...

...> > > > > > > > /dev/xvda1 -> /boot > > > > /dev/xvda2 -> a physical volume for LVM > > > > > > > > > > > > I added 5GB to this disk via Xencenter to extend /dev/xvda2. > > > > Usually I just have to do "pvresize /dev/xvda" to have the > > > > additional space added > > > to > > > > the disk. But for some reason it does not work for this disk. > > > > > > > > [root ~]# pvresize /dev/xvda > > > > Failed to find physical volume "...

I did not do pvresize because neither "pvs" or "pvdisplay" reported to have free space. After reboot they did, after which doing pvresize worked successfully. Sander Kuusemets University of Tartu, High Performance Computing, IT Specialist Skype: sander.kuusemets1 +372 737 5694 On 24/12/15 09:17,...

...gt; > I have a CentOS VM with only one disk on a Xenserver. > > The disk has 2 partitions: > > /dev/xvda1 -> /boot > /dev/xvda2 -> a physical volume for LVM > > > I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I > just have to do "pvresize /dev/xvda" to have the additional space added to > the disk. But for some reason it does not work for this disk. > > [root ~]# pvresize /dev/xvda > Failed to find physical volume "/dev/xvda". > 0 physical volume(s) resized / 0 physical volume(s) not resized >...

...quot; <bernard.fay at gmail.com> wrote: Hello, I have a CentOS VM with only one disk on a Xenserver. The disk has 2 partitions: /dev/xvda1 -> /boot /dev/xvda2 -> a physical volume for LVM I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I just have to do "pvresize /dev/xvda" to have the additional space added to the disk. But for some reason it does not work for this disk. [root ~]# pvresize /dev/xvda Failed to find physical volume "/dev/xvda". 0 physical volume(s) resized / 0 physical volume(s) not resized K Xvda does not seem to be re...

...gt; > The disk has 2 partitions: > > > > > > /dev/xvda1 -> /boot > > > /dev/xvda2 -> a physical volume for LVM > > > > > > > > > I added 5GB to this disk via Xencenter to extend /dev/xvda2. > > > Usually I just have to do "pvresize /dev/xvda" to have the > > > additional space added > > to > > > the disk. But for some reason it does not work for this disk. > > > > > > [root ~]# pvresize /dev/xvda > > > Failed to find physical volume "/dev/xvda". > > &gt...

Hi list, I have a SAN attached to a CentOS 4.2 server. I have expanded the size of the virtual disk within the SAN (by adding a new HD to the disk pool) and need CentOS to see the new size (CentOS see it as /dev/sdb). I'm using LVM. Do you know a method for the Volume Group to see that one of its harddisk is now bigger, without rebooting (it's not a problem with a reboot but since

This patch series allows you to shrink various objects, as requested in the following bugs: https://bugzilla.redhat.com/show_bug.cgi?id=585221 # resize2fs https://bugzilla.redhat.com/show_bug.cgi?id=585222 # pvresize https://bugzilla.redhat.com/show_bug.cgi?id=585223 # ntfsresize The first patch provides a consistent way to specify numbers with suffixes to guestfish, eg: truncate-size /foo 1G It also unifies the number parsing code used by 'alloc' and 'sparse' commands to use the same Gnul...

...replaced I need to move onto a new unit. My migration strategy at this time is to 1. Present a new LUN from the new SAN to all machines. 2. Make a PV with the new LUN. 3. Add it to the existing VG. 4. Use pvmove to move all the data from one PV to another. 5. Once the old LUN is empty, complete a pvresize to remove the old LUN. This all seems sound but looking for advice, specifically around the fact that the VG/PV data is being used by a number of machines/servers and the LV's are active on a number of different nodes. All the documentation/examples I can find assume a disk in a server, not a...