search for: resize2f

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)" and parse this output. It is known that resize2fs carries out...

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 blocks. How can I change the block size?...

Hello, As a Virtuozzo users we have majority of our diskspace formatted with -i 1024 -b 1024. Lately I discovered that on CentOS 4.6 ext2online barfs when I try to grow such filesystem. Running it with -v -d, it prints lots of lines like: ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2online: 873646830 is a bad size for an ext2 fs! rounding down to 873644033 ... group NNN inode table has

...+0300, Maxim Perevedentsev wrote: > Hello everyone! > > I am working on resizing qcow2 images using virt-resize+liguestfs. If you're shrinking, I believe a better way to do this is to sparsify the image. > 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)" and parse this output. > > It is known that...

...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 mkraid conflict with the journal? Is resize2fs even neccessary now-a-days? 3. If so, in the future, can ext3 compensate for a potential raid situation (reserving that meta-block) so that e2fsck and resize2fs won't be neccessary. Basically, Step 11 scares the hell out of me which is why I haven't done this on a live system. thanks, -e...

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: https://bugzilla.redhat...

...4675072163840, SEEK_SET) = 4675072163840 write(3, "\355A\350\3\0\20\0\0009\271\371M\206\177\0N\200\206\33M\0\0\0\0\350\3\2\0\10\0\0\0"..., 4096) = 4096 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 32719 root 20 0 785m 768m 792 R 98 20.0 2443:18 resize2fs $ sudo resize2fs /dev/mapper/data-data 3000G resize2fs 1.41.11 (14-Mar-2010) Resizing the filesystem on /dev/mapper/data-data to 786432000 (4k) blocks. Time passes. :D It's an LVM comprising 4x2TB disks in RAID10 and 4x500GB in RAID10. $ cat /proc/mdstat Personalities : [linear] [multipath...

Sometimes the user wants to know minimum size for dirty (e.g. mounted) filesystems. In this case, resize2fs -P will require calling e2fsck -f, while "in general, it is not safe to run e2fsck on mounted filesystems". Since resize2fs -P does not modify filesystem, we force it to display (probably approximate) minimum size. --- daemon/ext2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)...

...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

...them run over image (which may not have anything but filesystem) - I >>>> saw something like that in source. >>> Not sure I understand the question? >> As I understand, guestfs runs its own kernel-like daemon that can >> run its own commands. It is used to run e.g. resize2fs or e2fsck >> over loaded disk images. But those two utilities require the >> partition not to be mounted, so they are run by daemon and do not >> require anything to exists on partition. >> >> In API I found only the 'command' command which requires the >&g...

-------- Forwarded Message -------- Subject: Re: [Libguestfs] Question: running appliance commands over guest fs (resize2fs -P). Date: Tue, 15 Sep 2015 17:17:16 +0300 From: Maxim Perevedentsev <mperevedentsev@virtuozzo.com> To: Richard W.M. Jones <rjones@redhat.com> On 09/15/2015 04:57 PM, Richard W.M. Jones wrote: >> 2) More general, how to execute commands from appliance but make >> them...

Hi all, Can I ask if zerofree or resize2fs could also be applicable to ext4? Guestfish help of these two commands indicates that they are applicable to ext2/3. But ext4 is not covered in the help. However, I have tested these two commands in my Fedora 12 laptop, and it seems that both commands work well with ext4. So I don't quite unde...

...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) ] Where vmid is a parameter given to xm create. All work pretty well but resize2fs. Increasing DomU disk size consists in lvextend. That has been done. Rebooting DomU gives me additionnal free space on virtual disk. Here''s currently what I have: From Dom0: ## lvdisplay /dev/XEN/xps.101.disk # --- Logical volume --- # LV Name /dev/XEN/xps.101.disk #...

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%? Mo...

...lowing problem with my ext3 filesystem: - I had ext3 filesystem of the size of a few TB with journal. I correctly unmounted it and it was marked clean. - I then ran fsck.etx3 -f on it and it did not find any problem. - After increasing size of its LVM volume by 1.5 TB I resized the filesystem by resize2fs lvm_volume and it finished without problem. - But fsck.ext3 -f immediately after that showed "Inodes that were part of a corrupted orphan linked list found." and many thousands of "Inode XXX was part of the orphaned inode list." I did not accepted fix. According to debugfs all...

Greetings - I had a logical volume that was running out of space on a virtual machine. I successfully expanded the LV using lvextend, and lvdisplay shows that it has been expanded. Then I went to expand the filesystem to fill the new space (# resize2fs -p /dev/vde1) and I get the results that the filesystem is already xx blocks long, nothing to do. If I do a # df -h, I can see that the filesystem has not been extended. I could kick the users off the VM, reboot the VM using a GParted live CD and extend the filesystem that way, but I thought...

...▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒⟧ --:-- ********** Summary of changes: /dev/sda1: This partition will be resized from 512.0M to 510.0M. The filesystem ext2 on /dev/sda1 will be expanded using the 'resize2fs' method. /dev/sda2: This partition will be resized from 512.0M to 504.0M. The filesystem ext2 on /dev/sda2 will be expanded using the 'resize2fs' method. /dev/sda3: This partition will be resized from 512.0M to 503.7M. The filesystem ext2 on /dev/sda3 will be expanded using the &...

...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, - resize2fs on the VM Doing so, the kernel of the virtual machine seems not to see the space available for the partition has changed and resize2fs returns: "xvda already has xxxxxxxxx blocks, Nothing to do" This last until I hot remove the disk from the VM using xm block-detach and re-attach it...

...gt; >>them run over image (which may not have anything but filesystem) - I > >>saw something like that in source. > >Not sure I understand the question? > > As I understand, guestfs runs its own kernel-like daemon that can > run its own commands. It is used to run e.g. resize2fs or e2fsck > over loaded disk images. But those two utilities require the > partition not to be mounted, so they are run by daemon and do not > require anything to exists on partition. > > In API I found only the 'command' command which requires the > partition to be moun...

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 but that didn't give me the info...