similar to: how to resize a partition of a disk define as a physical volume

I should have added the output of pvs: [root ~]# pvs PV VG Fmt Attr PSize PFree /dev/xvda2 cl_vm731611 lvm2 a-- 9.00g 0 PFree still show 0. It should show 5g. Also: [root ~]# pvdisplay /dev/xvda2 --- Physical volume --- PV Name /dev/xvda2 VG Name cl_vm731611 PV Size 9.00 GiB / not usable 2.00 MiB Allocatable

How do you resize the partition without loosing data? gparted does not support LVM. On Wed, Feb 22, 2017 at 8:37 AM, SysAdmin <admin at s-s.network> wrote: > Hi, > > you need to resize partition /dev/xvda2, afterwards resize pv. > > Regards, > Holger > > > -----Urspr?ngliche Nachricht----- > > Von: CentOS [mailto:centos-bounces at centos.org] Im Auftrag

Hi, you need to resize partition /dev/xvda2, afterwards resize pv. Regards, Holger > -----Urspr?ngliche Nachricht----- > Von: CentOS [mailto:centos-bounces at centos.org] Im Auftrag von Bernard > Fay > Gesendet: Mittwoch, 22. Februar 2017 14:18 > An: CentOS mailing list > Betreff: Re: [CentOS] how to resize a partition of a disk define as a > physical volume > > I

On Wed, Feb 22, 2017 at 07:44:33AM -0500, Bernard Fay 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"

On Feb 22, 2017 7:45 AM, "Bernard Fay" <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

Hello everyone. I have the following problem that could help would appreciate. 1) Environment: HOST 1: xen-hypervisor-3.2-1-amd64 with all VM in LVM disk. HOST 2: XCP 0.5 2) The VM that I wish migrate is a domU in XEN and is debian lenny over LVM: ................................................................................................... # Configuration file for the Xen instance

Hi all, I try to use kernel 2.6.36.1 in HVM but building the drivers xen-blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16

Hi all, I try to use kernel 2.6.36.1 in HVM but building the drivers xen-blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16

I have a physical SLES11SP2/OES11 system that I''ve converted to a domU. It''s boots ok as an HVM, but when I try to boot as a PV it gets stuck. I have the kernel-xen packages installed and confident the menu.lst is correct. If I look at xm console for the VM I get the output below: Any ideas? Thanks James [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000]

I am running a Debian Squeeze Xen 4.0.1 Hypervisor and 2.6.32-5-xen-amd64 dom0. My xen-tools.conf: lvm = vg00 size = 100Gb # Disk image size. memory = 2048Mb # Memory size swap = 2G # Swap size # noswap = 1 # Don''t use swap at all for the new system. fs = ext4 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default

Hi, Not totally new to Xen but still very green and meeting some problems. Feel free to kick me to the DRBD people if this is not relevent here. I''ll be providing more info upon request but for now I''ll be brief. Debian/Squeeze running 2.6.32-5-xen-amd64 (2.6.32-21) Xen hypervisor 4.0.1~rc6-1 and drbd-8.3.8. One domU configured, with disk and swap image: root =

Good day. I''m getting this error: [101017.440858] blkfront: barrier: empty write xvda op failed [101017.440862] blkfront: xvda: barrier or flush: disabled [101017.463438] end_request: I/O error, dev xvda, sector 3676376 [101017.463452] end_request: I/O error, dev xvda, sector 3676376 [101017.463459] Buffer I/O error on device xvda1, logical block 459291 [101017.463464] lost page write

Hi! Say I export an LVM logical volume from dom0 as /dev/xvda to the domU: disk = [ ''phy:xenimages/stan,xvda,w'' ] No I can lvresize xenimages/stan in dom0, but the domU stays ignorant of this change. How could I propagate the resize to the domU without rebooting or temporarily breaking its connection to /dev/xvda? Sort of a SCSI rescan, perhaps? -- Thanks, Feri.

Hi. I added a disk to a hardware raid 5 array and now i want to expand the LVM physical volume. There are now 4 sas 146GB disks in the server. The virtual disk /dev/sdb from the raid controller has been resized successfully with the server management software osma. [root at srv1 ~]# fdisk -l /dev/sdb Disk /dev/sdb: 438.4 GB, 438489317376 bytes 255 heads, 63 sectors/track, 53309 cylinders

I mounted an iso file like so: ------------------------------------------- # mount -o loop=/dev/loop0 /path/to/iso /tmp/mnt #ls /tmp/mnt cdromupgrade  dists  doc  install  isolinux  md5sum.txt  pics  pool  preseed  README.diskdefines  ubuntu ------------------------------------------- I used the following file to try to have pygrub boot the mounted iso: -------------------------------------------

When virtio-blk device is resized from host (using block_resize from QEMU) emit KOBJ_CHANGE uevent to notify guest about such change. This allows user to have custom udev rules which would take whatever action if such event occurs. As a proof of concept I've created simple udev rule that automatically resize filesystem on virtio-blk device. ACTION=="change", KERNEL=="vd*",

When virtio-blk device is resized from host (using block_resize from QEMU) emit KOBJ_CHANGE uevent to notify guest about such change. This allows user to have custom udev rules which would take whatever action if such event occurs. As a proof of concept I've created simple udev rule that automatically resize filesystem on virtio-blk device. ACTION=="change", KERNEL=="vd*",

Hi experts, First I post my log root@intel_5500_server:/> ifconfig eth0 Link encap:Ethernet HWaddr 00:15:17:BB:5E:88 inet addr:128.224.165.205 Bcast:128.224.165.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:febb:5e88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2375 errors:0 dropped:0 overruns:0 frame:0

Hi, Sorry for the need of the long winded email. Looking for some answers to the following. I am setting up a xen PV domU on top of a LVM partitioned DRBD device. Everything was going just fine until I tried to test the filesystems in the domU. Here is my setup; Dom0 OS: CentOS release 5 (Final) Kernel: 2.6.18-8.1.4.el5.centos.plusxen Xen: xen-3.0.3-25.0.3.el5 DRBD:

Hi all I want to shrink one of my LVM based domU''s, but don''t quite know how to do it. I have searched the Wiki & HOWTO''s, and they all show you how expand / enlarge a LVM based domU, but not shrinking it. So, I stopped (destroyed) the domU, and then resized it as follows: lvresize /dev/data/cpanel1 -L10GB (It was 100GB), but when I a started it up again, I