similar to: [PATCH 0/4] Allow shrinking of ext2, PVs and NTFS

I'm pleased to announce a major new release of libguestfs. libguestfs is a library and a set of tools for accessing and modifying disk images and virtual machines. You can use this for viewing and editing files inside guests, scripting changes to VMs, monitoring disk used/free statistics, P2V, V2V, performing partial backups, cloning VMs, and much more. Home page: http://libguestfs.org/

This creates a generic partition table interface. One immediate advantage is that you can create GPT partitions which can be larger than 2 TB. For example, here is a 1 exabyte partition: ><fs> sparse /mnt/tmp/test/test.img 1E ><fs> run ><fs> part-init gpt /dev/vda ><fs> part-add /dev/vda primary 0 0 ><fs> list-devices /dev/vda

Handle the swap partition on their own, rebuilding them using the existing UUID and label. --- resize/resize.ml | 35 ++++++++++++++++++++++++++++------- resize/virt-resize.pod | 8 ++++++++ 2 files changed, 36 insertions(+), 7 deletions(-) diff --git a/resize/resize.ml b/resize/resize.ml index 7d06f18..59ee5bf 100644 --- a/resize/resize.ml +++ b/resize/resize.ml @@ -60,6 +60,7 @@ and

Hello guys! I tried to shrink a partition when resizing an image using virt-resize. The numbers and result are weird. ================BEFORE================ ><fs> blockdev-getsize64 /dev/sdc 4294967296 ><fs> part-list /dev/sdc [0] = { part_num: 1 part_start: 65536 part_end: 2193555455 part_size: 2193489920 } [1] = { part_num: 2 part_start: 2193555456

Use resize.f2fs (via f2fs_expand) to expand f2fs filesystems, if available. --- resize/resize.ml | 12 ++++++++++-- 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

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

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

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 Mon, Apr 27, 2020 at 10:13:37 +0200, Paul van der Vlis wrote: > Op 27-04-2020 om 09:02 schreef Peter Krempa: > > On Sat, Apr 25, 2020 at 16:40:35 +0200, Paul van der Vlis wrote: > >> Op 25-04-2020 om 16:00 schreef Paul van der Vlis: > >>> Hello, > >>> > >>> I have a qcow2 disk what needs to become increased. > >>> >

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

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, Gordon Messmer wrote: > On 12/21/2015 11:15 AM, Sander Kuusemets wrote:

When fetching a storage volume over SSH, we were detecting its size with a simple 'stat -c %s'. While this works fine for files, it won't return the correct size of a block device. This patch uses the output of 'blockdev --getsize64' for block devices, and stat as before for regular files. Fixes RHBZ#620698 --- lib/Sys/VirtV2V/Transfer/SSH.pm | 16 +++++++++++++++- 1 files

Hi! Company behind PVS-Studio analyzed relatively recent version of LLVM and some results are reported in http://www.viva64.com/en/b/0446/. Eugene.

The appliance has no LVM system ID set, which means that lvm commands will ignore VGs with a system ID set to anything. Since we want to work with them, pass --foreign at least when listing them to see them. See also lvmsystemid(7). --- daemon/lvm.c | 10 ++++++---- generator/daemon.ml | 1 + 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/daemon/lvm.c b/daemon/lvm.c

Hi, Jonas! On Tue, Nov 1, 2016 at 3:26 AM, Jonas Wagner <jonas.wagner at epfl.ch> wrote: > Hi Eugene, > > I think this is really cool! You've convinced me to try out PVS on some of > my own projects :) > > Of all the warnings presented in the article, there was one for which I > thought it's a false positive. By default, LLVM is compiled without RTTI and >

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

On Tue, Jul 26, 2016 at 05:41:28PM +0200, Pino Toscano wrote: > The appliance has no LVM system ID set, which means that lvm commands > will ignore VGs with a system ID set to anything. Since we want to work > with them, pass --foreign at least when listing them to see them. > > See also lvmsystemid(7). This is sort of a hack, if I'm understanding correctly. Can we not

On Wed, Nov 2, 2016 at 9:41 AM, Jonas Wagner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hello, > > I think this should be added by Clang itself. > > > I don't think so. There are several sources online that indicate that > developers need to *manually* specify std::nothrow. If they don't, > operator new will throw an exception even if code is

Hello, I've noticed a strange delay while booting a CentOS 7 guest on a CentOS 7 host with slow disks (7200RPM) with write cache off. The guest and host are freshly installed Centos 7 (host was fully patched before guest install). Guest is installed on an lvm pool residing on an md raid1 with two SATA 7200 RPM drives with their write caches off. The delay is on mounting /boot, the dmesg

This requires changing the generator so it can handle passing optional arguments all thr way through to the daemon, changing the protocol (see previous patch set), and implementing the new mkfs-opts call. At the moment there is just an optional blocksize argument, thus mimicking what you can already do with 'mkfs-b'. But this change will allow us in future to encode much of the rest of