public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
* [rpms/zerofree] epel10: Upgrade to 1.1.0
@ 2026-06-15 0:17 Robert Scheck
0 siblings, 0 replies; only message in thread
From: Robert Scheck @ 2026-06-15 0:17 UTC (permalink / raw)
To: git-commits
A new commit has been pushed.
Repo : rpms/zerofree
Branch : epel10
Commit : 20082ff14a31b51f60a8dedfee277453fcebde4e
Author : Robert Scheck <robert@fedoraproject.org>
Date : 2018-02-19T21:08:03+01:00
Stats : +36/-88 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/zerofree/c/20082ff14a31b51f60a8dedfee277453fcebde4e?branch=epel10
Log:
Upgrade to 1.1.0
---
diff --git a/index.html b/index.html
index c779213..2a0b312 100644
--- a/index.html
+++ b/index.html
@@ -1,5 +1,10 @@
<html>
<head>
+<!--
+ Support idiotic mobile browsers that are incapable of rendering
+ straightforward HTML properly
+-->
+<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Keeping filesystem images sparse</title>
</head>
<body>
@@ -51,14 +56,13 @@ all the free space:
The disadvantage of <code>dd</code> in this context is that it destroys
any sparseness that exists: free blocks that were originally represented
as holes in the image file are replaced with actual blocks containing
-zeroes.
+zeroes. Also, filling up a live filesystem is probably a bad idea.
<p>
As an alternative approach, and as practice in mucking about with ext2
filesystems, I've written a utility which scans the free blocks in an
ext2 filesystem and fills any non-zero blocks with zeroes.
-The source, <a href="zerofree-1.0.3.tgz">zerofree-1.0.3.tgz</a>, is
-available for download. It's also available in a git repository:
-<code>git clone http://intgat.tigress.co.uk/rmy/git/zerofree.git</code>
+The source, <a href="zerofree-1.1.1.tgz">zerofree-1.1.1.tgz</a>, is
+available for download.
<p>
<ul>
<li>A cautious user would run fsck on the filesytem both before and after
@@ -66,77 +70,29 @@ running zerofree.
<li>The filesystem to be processed should be unmounted or mounted read-only.
<li>The utility also works on ext3 or ext4 filesystems.
<li>Binary packages are available in the standard repositories for Debian and Fedora.
-<li>The <a href="http://partedmagic.com">Parted Magic</a> live distribution includes zerofree.
+<li>The <a href="http://www.sysresccd.org/SystemRescueCd_Homepage">SystemRescueCd</a> live distribution includes zerofree.
+<li><a href="http://libguestfs.org/">guestfish</a> can run zerofree on many types of virtual machine filesystems.
</ul>
<p>
-Better than either of these would be to have the guest kernel keep the free
-blocks empty. My original inspiration was the
-<a href="http://www.uwsg.iu.edu/hypermail/linux/kernel/0401.3/1058.html">
-ext2fs privacy (i.e. secure deletion) patch</a> described in a Linux
-kernel mailing list thread. I've also made use of a later patch for ext3
-entitled
-<a href="http://marc.theaimsgroup.com/?l=linux-fsdevel&m=113986429313502&w=2">Secure Deletion Functionality in ext3</a>
-from the linux-fsdevel mailing list. (See also the authors' paper on
-<a href="http://www.filesystems.org/project-sdfs.html">Secure Deletion File Systems</a>.)
-I've modified the patches to make them more suitable for the present purpose.
-<ul>
-<li><a href="linux-2.6.25-zerofree2.patch">linux-2.6.25-zerofree2.patch</a> (for ext2 filesystems)</li>
-<li><a href="linux-2.6.25-zerofree3.patch">linux-2.6.25-zerofree3.patch</a> (for ext3 filesystems)</li>
-</ul>
-When a filesystem is mounted with the <code>zerofree</code> option (added
-by these patches) all the blocks freed when a file is deleted are filled
-with zeroes.
-Remember, this extra work will hurt disk performance.
-Note that the ext3 patch doesn't support data journalling
-mode, so deleted metadata isn't zeroed. It also hasn't been tested
-as thoroughly as the patch for ext2. And neither has been maintained for a
-very long time.
-<p>
-However, the above techniques are only half the story: the empty free
+However, this is only half the story: the empty free
blocks still consume space in the underlying filesystem, so something
-must to be done to reclaim that space. For filesystems and kernels that
-support it the fallocate call with <code>FALLOC_FL_PUNCH_HOLE</code> can
-be used to deallocate space in a file.
+must to be done to reclaim that space.
<p>
-An existing alternative is to use the sparse file handling capabilities
+A common suggestion is to use the sparse file handling capabilities
of the GNU <code>cp</code> command to take a copy of the filesystem image with
<code>cp --sparse=always</code> (though this does require the original
and sparse files to exist at the same time, which may be inconvenient).
<p>
-As an alternative alternative I've written a utility which can make
-any specified files on an ext2 filesystem
-sparse, <a href="sparsify.c">sparsify.c</a>. This doesn't require any
-additional disk space to work its magic, but it does require that the
-filesystem containing the filesystem image is unmounted, which is just a
-different sort of inconvenience.
-<p>
-<ul>
-<li>The usual disclaimers apply: this worked for me when I tested it but it
-might destroy your data.</li>
-<li>Versions of libext2fs prior to 1.41 do not support ext4;
-later versions should work with all filesystem types.</li>
-<li>In 1.41 the progress monitor may exceed 100% as the iterator visits some
-blocks more than once.</li>
-<li>The code doesn't support huge (>2TB) files. It will issue a warning and
-refuse to process them.</li>
-</ul>
-<p>
-As an example, suppose we have an unmounted filesystem
-image, <code>fs.image</code>, in the directory <code>/data</code>, which is the
-root of the <code>/dev/hda2</code> filesystem. We can reclaim deleted
-blocks and make it sparse like so:
-<p>
-<pre>
- zerofree /data/fs.image
- umount /data
- sparsify /dev/hda2 /fs.image
- mount /data
-</pre>
+If your kernel and util-linux are sufficiently modern and you have a supported
+filesystem you can use <code>fallocate -d</code> to 'dig holes' in a file.
+This makes the file sparse in-place, without using extra disk space.
<p>
<hr>
<address>
-<a href="mailto:rmy@tigress.co.uk">Ron Yorston</a><br>
-9th August 2012
+<a href="mailto:rmy@pobox.com">Ron Yorston</a><br>
+18th April 2004 (updated 19th February 2018)<br>
+Some <a href="obsolete.html">obsolete</a> information has been moved to a
+separate page.
</address>
</body>
</html>
diff --git a/sources b/sources
index 38a03b9..292fc5d 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-7fffca9639a2acc9c889c49b3f94a0c6 zerofree-1.0.3.tgz
+SHA512 (zerofree-1.1.0.tgz) = 5be670ad0bc12d9876554756cd2718d366adb7cb1b7cb3a3a59f60a47645ccc8c85760dc3afc368664aa658e23f8b39f81fb505b34a59ac82c4b2861f958231a
diff --git a/zerofree.spec b/zerofree.spec
index 6c2cc60..62c32bb 100644
--- a/zerofree.spec
+++ b/zerofree.spec
@@ -1,14 +1,14 @@
-Summary: Utility to force unused ext2 inodes and blocks to zero
+Summary: Utility to force unused ext2/3/4 inodes and blocks to zero
Name: zerofree
-Version: 1.0.3
-Release: 10%{?dist}
-License: GPL+
+Version: 1.1.0
+Release: 1%{?dist}
+License: GPLv2
-URL: http://intgat.tigress.co.uk/rmy/uml/
+URL: https://frippery.org/uml/
-Source0: http://intgat.tigress.co.uk/rmy/uml/%{name}-%{version}.tgz
-Source1: http://intgat.tigress.co.uk/rmy/uml/sparsify.c
-Source2: http://intgat.tigress.co.uk/rmy/uml/index.html
+Source0: https://frippery.org/uml/%{name}-%{version}.tgz
+Source1: https://frippery.org/uml/sparsify.c
+Source2: https://frippery.org/uml/index.html
# zerofree.sgml is the source for the man page from Debian.
# Unfortunately we cannot build this in Fedora because of an apparent
@@ -18,16 +18,12 @@ Source3: zerofree.sgml
Source4: zerofree.8
BuildRequires: e2fsprogs-devel
-%if 0%{?rhel} == 5
-BuildRequires: e4fsprogs-devel
-Group: Applications/System
-%endif
%description
zerofree is a utility to set unused filesystem inodes and blocks of an
-ext2 filesystem to zero. This can improve the compressibility and
-privacy of an ext2 filesystem.
+ext2/3/4 filesystem to zero. This can improve the compressibility and
+privacy of an ext2/3/4 filesystem.
This tool was inspired by the ext2fs privacy (i.e. secure deletion)
patch described in a Linux kernel mailing list thread.
@@ -41,19 +37,11 @@ should be careful.
%setup -q
cp -p %{SOURCE1} .
cp -p %{SOURCE2} .
-%if 0%{?rhel} == 5
-sed -e 's@ext2fs/ext2fs.h@ext4fs/ext2fs.h@' -i zerofree.c sparsify.c
-sed -e 's@-lext2fs@-lext4fs@' -i Makefile
-%endif
%build
make CC="gcc $RPM_OPT_FLAGS"
-%if 0%{?rhel} == 5
-gcc $RPM_OPT_FLAGS sparsify.c -o sparsify -lext4fs
-%else
gcc $RPM_OPT_FLAGS sparsify.c -o sparsify -lext2fs
-%endif
%install
@@ -63,13 +51,17 @@ install -D -p -m 644 %{SOURCE4} $RPM_BUILD_ROOT%{_mandir}/man8/zerofree.8
%files
-%doc COPYING index.html
+%license COPYING
+%doc index.html
%{_sbindir}/zerofree
%{_sbindir}/sparsify
%{_mandir}/man8/zerofree.8*
%changelog
+* Mon Feb 19 2018 Robert Scheck <robert@fedoraproject.org> - 1.1.0-1
+- Upgrade to 1.1.0
+
* Fri Feb 09 2018 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.3-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2026-06-15 0:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-06-15 0:17 [rpms/zerofree] epel10: Upgrade to 1.1.0 Robert Scheck
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox