similar to: Is zerofree or resize2fs applicable to ext4?

Hi- Is it safe to use the zerofree utility on an ext4 partition inside an LVM with guestfish? I know zerofree works on ext4, but I am unsure about LVM. The info page uses the syntax "zerofree <device>", so using the info page example, could I (safely) do something like the following? $ guestfish Welcome to guestfish, the libguestfs filesystem interactive shell for

zerofree is a package that can take an ext2 (only?) filesystem, work out what parts of the filesystem are not used, and either zero them or sparsify them. This was useful in about 2009 when I added it to Fedora. However nowadays it's more convenient to use the equivalent kernel functionality (via the ‘fstrim’ command or equivalent ioctls). The kernel functionality also works correctly for

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:

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,

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

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

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

Hello Richard, On Sun, 18 Feb 2018, Richard W.M. Jones wrote: > If you wish to take it over, I can orphan it instead. I'm happy to take zerofree. Regards, Robert

On Sun, 18 Feb 2018, Richard W.M. Jones wrote: > There's also a more serious data safety issue: Although this probably > works OK for ext2 since that format is frozen in time, it probably > corrupts ext4 filesystems containing features that it doesn't know > about. > > It is for these reasons that I don't think you should use this package > and I intend to retire

On 09/15/2015 05:37 PM, Richard W.M. Jones wrote: > On Tue, Sep 15, 2015 at 05:17:16PM +0300, Maxim Perevedentsev wrote: >> On 09/15/2015 04:57 PM, Richard W.M. Jones wrote: >>>> 2) More general, how to execute commands from appliance but make >>>> them run over image (which may not have anything but filesystem) - I >>>> saw something like that in

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, yesterday I experienced following 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

Hi all, I am trying to compile libguestfs from source in Fedora12, but failed with such error: cp: cannot stat `initramfs/fakeroot.log': No such file or directory make[2]: *** [../initramfs/fakeroot.log] Error 1 make[2]: Leaving directory `/home/yufang/Code/libguestfs/appliance' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/yufang/Code/libguestfs' make: ***

Is there a utility to zero unused blocks on a disk? CentOS 6.7/Ext4 I saw zerofree, but I?m not sure it would work on Ext4 or even work on this version of CentOS. thanks, -wes

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

I found a thread that has almost the exact same symptoms as me, but didn't seem to come to a resolution: https://listman.redhat.com/archives/ext3-users/2004-December/msg00018.html I have an LVM(2) array that I've just lvextend'd and want to resize2fs, but I can't get through the e2fsck. I get these errors when fsck-ing: Group 3125's inode table at 102400545 conflicts with

On Tue, Sep 15, 2015 at 04:31:46PM +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 >

On 09/02/16 12:08 AM, g wrote: > > > On 02/08/16 15:34, Wes James wrote: >> Is there a utility to zero unused blocks on a disk? >> >> CentOS 6.7/Ext4 >> >> I saw zerofree, but I?m not sure it would work on Ext4 or even work on >> this version of CentOS. >> >> thanks, >> > . > a comment on replies to your post. > > i find

On Fri, Apr 18, 2014 at 06:56:57PM +0200, Patrik Horn?k wrote: > > yesterday I experienced following 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