similar to: virt-resize corrupts ext2 filesystem

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

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

Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- resize/resize.ml | 82 +++++++++++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 72 insertions(+), 10 deletions(-) diff --git a/resize/resize.ml b/resize/resize.ml index 3f804a0..ea0be9e 100644 --- a/resize/resize.ml +++ b/resize/resize.ml @@ -596,6 +596,8 @@ read the man page virt-resize(1). let hash = Hashtbl.create 13

Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- resize/resize.ml | 84 +++++++++++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 74 insertions(+), 10 deletions(-) diff --git a/resize/resize.ml b/resize/resize.ml index cc76aa0..fc622ba 100644 --- a/resize/resize.ml +++ b/resize/resize.ml @@ -596,6 +596,8 @@ read the man page virt-resize(1). let hash = Hashtbl.create 13

--- daemon/daemon.h | 1 + daemon/labels.c | 3 +++ daemon/swap.c | 21 +++++++++++++++++++++ generator/actions.ml | 4 ++++ 4 files changed, 29 insertions(+) diff --git a/daemon/daemon.h b/daemon/daemon.h index 79a5288..2379e31 100644 --- a/daemon/daemon.h +++ b/daemon/daemon.h @@ -254,6 +254,7 @@ extern int64_t ntfs_minimum_size (const char *device); /*-- in swap.c --*/

We?ve been seeing this a lot lately on generic CentOS 6 rpm installs: rpm -qa | grep libguestfs libguestfs-java-1.16.19-1.el6.x86_64 libguestfs-java-devel-1.16.19-1.el6.x86_64 libguestfs-1.16.19-1.el6.x86_64 libguestfs-tools-1.16.19-1.el6.x86_64 libguestfs-javadoc-1.16.19-1.el6.x86_64 libguestfs-devel-1.16.19-1.el6.x86_64 libguestfs-tools-c-1.16.19-1.el6.x86_64

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 +

Hello everyone! I am working on resizing qcow2 images using virt-resize+liguestfs. E.g. I when shrinking a partition, I have to resize filesystem using resize2fs-size. The problem is that I cannot find out minimal partition size (aka resize2fs -P). The only way is calling "resize2fs-size 1K", wait for resize2fs to claim "resize2fs: New size smaller than minimum (510050)"

Hi All: I am trying to resize a centos (5.2) VM drive. I use VMware and I have increased the size of the drive by 40G. I am running resize2fs on /dev/sdb1 (which is my root partition) but when I do I get this error: [root at centos ~]# resize2fs /dev/sdb1 120G resize2fs 1.39 (29-May-2006) The containing partition (or device) is only 19970795 (4k) blocks. You requested a new size of 31457280

I have a file system I am trying to resize via resize2fs but I get this error resize2fs 1.41.14 (22-Dec-2010) resize2fs: New size too large to be expressed in 32 bits im on debian squeeze 2.6.32-5-amd64 # pvs ? PV???????? VG????? Fmt? Attr PSize? PFree ? /dev/md1?? vgRAID6 lvm2 a-?? 18.17t 134.12g # lvs ? LV??? VG????? Attr?? LSize? Origin Snap%? Move Log Copy%? Convert ? data1 vgRAID6 -wi-ao

Hello everybody, I''m playing with Xen and trying to extend DomU disk space. My Configuration: Dom0: all Xen machine are HVM. They''re installed on LVM. I''ve one VG (XEN) on Dom0 and created a LV (here, xps.101.disk) per DomU. disk configuration in xen conf is as follow: disk = [ ''phy:/dev/XEN/xps.%d.disk,ioemu:hda,w'' % (vmid)

Hello, I am using Xen 4.0.1 and Xen 3.2.1 dom0 with Debian Lenny and Squeeze dom0s. I have a bunch of virtual machines running , all using LVM as backend storage. Mostly, an LVM logical volume is mapped to a partition in the VM (eg: xvda1) I have tried to hot resize the filesystem in the VM without umounting it but it just do not work... Here is what I did: - lvextend on the dom0, -

Consider this section: http://www.tldp.org/HOWTO/Software-RAID-HOWTO-4.html#ss4.14 I have not done this before and I'm leary about Step 11 which is resizing the filesystem after doing a mkraid command. This howto lacks any ext3 documentation. Some questions I have are: 1. Should I convert back to ext2 on all my filesystems before I do a mkraid? 2. If I leave the system at ext3, will the

Hullo! First mail, sorry if this is the wrong place for this kind of question. I realise this is a "piece of string" type question. tl;dr version: I have a resizefs shrinking an ext4 filesystem from ~4TB to ~3TB and it's been running for ~2 days. Is this normal? Strace shows lots of:- lseek(3, 42978250752, SEEK_SET) = 42978250752 read(3,

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

On May 06, 2016, at 12:29 PM, John R Pierce <pierce at hogranch.com> wrote: On 5/6/2016 11:19 AM, Wes James wrote: 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. what file system type is this /dev/lvname/root ? I tried to find the type from blkid /dev/sda4

https://bugzilla.redhat.com/show_bug.cgi?id=755729 This bug reports that the error message printed by the resize2fs API calls (which comes directly from the resize2fs command) says: Please run 'e2fsck -f /dev/vda1' first. That command is not possible from guestfish (where it would be 'e2fsck-f' or 'e2fsck ... forceall:true'). Fixing that bug caused this bug:

Hello Mailing List! A quick question. Has anyone gotten a resize (in my case grown) a Xen DomU disk image? Here is the procedure I have followed: 1. Install a DomU using virt-install Customize xvda to be all one partition ext3 2. On Dom0: dd if=/dev/zero bs=1G count=1 >> <my_disk_image> ll -h (Image is now 1GB larger) xm create <DomU> On DomU: df -h (Size has not

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

Tweak the error message "e2fsck -f" and "e2fsck -fy" to "e2fsck-f" and "e2fsck-fy". Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/ext2.c | 20 ++++++++++++++++++-- 1 files changed, 18 insertions(+), 2 deletions(-) diff --git a/daemon/ext2.c b/daemon/ext2.c index 79fd354..9fe938e 100644 --- a/daemon/ext2.c +++ b/daemon/ext2.c