dump-announce

[Dump-announce] Dump/restore 0.4b52 release

[Tim W. <sou...@wo...>]

Hi everyone,

I've pushed 0.4b52 today. This is a minor release that fixes all the 
remaining issues that valgrind reports. There was nothing major, the 
vast majority were memory that wasn't freed before the program exits. A 
few minor memory leaks, one read beyond the end of a buffer (but the 
value read wasn't used) and some uninitialized memory reads where 
structures are written to tape.

I have changed the way the workers communicate while writing to tape. I 
wasn't able to work out why but the previous method of synchronizing the 
workers didn't work reliably under valgrind and regularly lead to 
corrupted tapes where data was written out of order. This change 
shouldn't cause any differences or problems but if you do see problems 
with this release - most likely related to dump locking up and never 
completing - then this change is likely the culprit.

Tim.

[Dump-announce] Dump/restore 0.4b51 release

[Tim W. <sou...@wo...>]

Hi everyone,

You didn't expect to hear from me again so soon but dump0.4b51 has been 
released today.

There was a potential buffer overflow introduced in restore in version 
0.4b48 (sorry!).

This doesn't affect dump and there's no problem continuing to use 0.4b48 
through 0.4b50 for backups, but people should consider upgrading to 
0.4b51 if they're restoring critical files.

Chances are, if you trip over this bug, restore will fail in obvious 
ways, but due to the nature of buffer overflows, it's possible that the 
only symptom will be a silently corrupted restored file.

You are less likely to have a problem if the tape is compressed (using 
dump's compression).

Special thankyou to Michael Orlitzky who has been porting dump to the 
musl standard library who encountered this and has been invaluable in 
helping track down this issue which I could not reproduce locally. Only 
once we'd worked out where the problem was did I manage to trigger a 
failure in valgrind.

Tim.

[Dump-announce] Dump/restore 0.4b50 release

[Tim W. <sou...@wo...>]

Hi everyone,

The 0.4b50 release of dump/restore has been published. (The date in the 
manpages says "version 0.4b50 of 22 Mar 2025". I didn't expect to get 
time to publish until the weekend but all the tests completed last night 
and I got a bit of spare time today so you get it early)

For most people there's little of interest here unless you're having 
problems restoring old dumps where there's a few fixes:

1. A new command line option --ignore-compression-flag-for-0.4b45-dumps 
for restore that allows dumps writen with "compression" by v0.4b45 to be 
restored.  This flag should not be used in any other context - it won't 
help!  Thankyou to Greg for his update on bug #169 which lead to this.

2. The Archive file was not padded to a whole number of tape blocks. 
This means that 0.4b49 could not use archive files unless they happened 
to be the correct length.

3. Tapes written with compression header bitfields that are not in amd64 
gcc order can now be read. This was supposed to work in 0.4b49 but a bug 
meant that it only worked for amd64 gcc ordered bitfields. 0.4b49 
removed the compiler dependency and ensured the bitfields were always 
written in the amd64 gcc order.

There's one bugfix - which has been patched in debian for ages: QFAfiles 
for real tapes always had a zero tape position. I inadvertently dropped 
this completely while bringing in the debian fixes to 0.4b49.  Thankyou 
to Alexander Zangerl for spotting my mistake.


And there's two new command line options to dump:
--filesys-name - which lets you set the text of the dump to replace the 
default "an unlisted filesystem". This is particularly aimed at people 
who dump from snapshots which do not appear in fstab or mtab.

--dumpdates-time - which sets the time of the dump to that supplied on 
the command line instead of dump using the current time when it starts. 
There's a race condition related to dumping from snapshots that this 
resolves (see below for details of the race condition for anyone who 
thinks they might be impacted)


See NEWS for more details of the changes in this release.


I haven't fully tested all the long command line options. They should 
all be documented in the man pages. I'll give a credit in the next NEWS 
file for anyone who finds any where I've made a mistake and it doesn't 
work the same way as the single character option. File a bug on the 
sourceforge page or email me or one of the dump lists.

-------

Race condition related to dump timestamps and snapshots:

Day 1 level 0 dump: (assume this starts at 00:00:00 on day 1)
1. Take a snapshot of the filesystem at D1-00:00:00

A file now changes on the underlying filesystem - this change is not 
visible in the snapshot - the file has the modification time of 
D1-00:00:01

2. Dump starts at D1-00:00:02 and writes this timestamp into dumpdates. 
The level 0 dump completes and verifies correctly against the snapshot.


Day 1 level 1 dump: (assume this starts at 00:00:00 on day 2)
1. Take a snapshot of the filesystem at D2-00:00:00

2. Take the level 1 dump. All files that have changes between 
D1-00:00:02 and D2-00:00:00 will be included in the dump. The file with 
the D1-00:00:01 timestamp is missed and never gets included in any 
incremental dump (unless the file changes again)



In order to avoid this issue, --dumpdates-time should be set to the time 
of the snapshot (which will likely be a few seconds earler than dump 
would have written to dumpdates.


N.B.  There are plenty of other issues related to taking a dump of a 
live filesystem that this commandline flag doesn't solve but many of us 
do take snapshots of a live file system to dump it.

[Dump-announce] Dump/restore 0.4b49 release

[Tim W. <sou...@wo...>]

Hi everyone,

The 0.4b49 release of dump/restore has been published.

IMPORTANT: Earlier versions of restore will not be able to read dumps
made by 0.4b49. (But 0.4b49 can read old tapes)

This is mostly minor bug fixes but there are two significant changes:

1. There has been a complete reworking of how restore reads from
tape/file. There is now only a single set of functions which do not
depend on detecting whether the dump is from a tape or a file. In
particular this now makes it possible to write a dump to a file and then
later write it to tape as restore is agnostic to precisely how the data
is blocked by the tape.
As a result the -l option of restore has gone. If you were using it
previously in a script the option will have to be removed.

2. There has been a change in the way dump records how many following
blocks on the tap belong to the inode we are processing. Previously
there was a 512 byte block which used one bit per byte - so we had an
"administrative" (TS_ADDR) record for each 512K of data. Now that block
encodes runs of blocks. In extremis, we can record 256*16384=4M blocks
(4G of data) per TS_ADDR record. This very dramatically reduces the
amount of tape used to store large sparse files - the 5T-sparse test
goes from using 10G of tape to a few hundred K of tape, almost all of
which was (and still is) overhead.
The encoding used is 100% compatible, so old tapes can be read without
issue.

One minor change might help people who backup to tape - previously dump
(incorrectly) wrote incompressible blocks that were bigger than the -b
setting given to dump and likewise, restore tried to read larger blocks.
Now, if this happens, dump will split the block into two tape blocks and
restore will not try to read extra data that the tape drive might
reject without returning anything at all.
You were very unlikely to encounter the dump problem, due to the
inefficient recording of the metadata, larger tape block sizes were
inevitably compressible but with the change above this becomes much more
likely to happen. If it does you'll see a line of trace like this:
Incompressible block could not be written to tape. Splitting it You will
only get this if your -b setting matches the maximum the tape drive
supports, you're using dump's compression, AND the data it's writing to
tape cannot be compressed. (Note that dump continues to write a single
block bigger than the -b setting if the tape drive accepts it.  But if
the block is rejected dump tries again after splitting it)
Previously you could not restore with -b set to the maximum the tape
drive supported if the tape was compressed.

There is a minor change made mostly for my convenience, when restoring,
it will now print a status line every 5 minutes. This doesn't have much,
if any, useful information in it for most but makes it clear that
restore is doing something rather than just hung.

...
RESTORE: Block 5225416401 read on volume 5 (inode 12 block 5225415911)
RESTORE: Block 5313177318 read on volume 5 (inode 12 block 5313176828)

I don't think this should cause any issues anywhere, but if it does
cause problems then file a bug and I'll do a quick release that removes
it again.

I've merged in many patches from the debian version of dump/restore.
Special thanks to Alexander Zangerl for maintaining this - and to the
people who proposed patches, where possible I've tried to name them in
the git history. Apologies if I've missed anywone or atttributed patches
incorrectly.

I also reverted one minor fix I made in the previous release - corrupted
sparse files with a hole at the start written with dump 0.4b40-0.4b42
cannot, as I though previously, be automatically repaired as the repair
depends on the block size of the filesystem dump was reading from which
is not recorded on the tape. If anyone has an old tape with sparse files
on it that they need to repair then contact me and I can talk you
through how to (try to) manually repair them after restoring them. Note
that it's impossible for dump to even detect that some files have been
corrupted although they will be very small.

See NEWS for details of most of the more minor changes.

[Dump-announce] Dump/restore 0.4b48 release

[Tim W. <sou...@wo...>]

Hi everyone,

The 0.4b48 release of dump/restore has been published today containing
fixes for almost a decade of outstanding bugs, mostly as a result of
incomplete ext4 support but a few were present in ext3 too.

This is likely the last release that nominally supports anything other
than linux systems. If anyone is successfully using dump/restore on a
non-linux system then please let me know and I'll see what can be done
but my belief and understanding from looking at the code is that
dump/restore does not work on non-linux systems. (Please also take note
of the code commented by #if 0 in bsdcompat.h which likely introduces an
incompatibility with older versions of dump/restore on non-linux systems
and possibly needs adding back.)

I have added a fairly extensive regression suite, not in the tarball but
available via git in the testcases/ directory. These require root to run
and reformat block devices, so "handle with care".

Thanks to all bug reporters.

And a special thank you to Stelian and Mike for maintaining dump/restore
over many, many years.

Full changelog below.

Regards,

Tim.


Changes between versions 0.4b47 and 0.4b48 (released Oct 20, 2024)
===================================================================
1.	Handle fs with more than 2^32 blocks (Greg Oster)

2.	Handle EA stored in blocks with address >2^32.

3.	Handle the case were EAs are stored across two blocks. Fixes several
 	reported bugs regarding the restore of directory attributes.
 	Additionally, now restore -C passes too. Originally restore -C was
 	patched for files, but not directories, in debian bug#940473 by
 	Alexander Zangerl.  Substantially redone and extended to directory
 	attributes here.

4.	Do not record garbage data in dump for files with
 	EXT2_EXTENT_FLAGS_UNINIT set indicating that the disk block has not
 	been written to and should be assumed to be all zeros.

5.	Dump small files on ext4 partitions with -O inline-data set.

6.	Major performance enhancements on the restoring and verifying of very
 	sparse files.

7.	Handle dumps that are over 2^32 (tape) blocks long (>4T)

8.	Handle restoring sparse files that start with a hole from dump versions
 	0.4b42/43. Previously they were restored but corrupted as some of the
 	initial hole was moved to the end.

9.	Many cleanups. Move to autoconf v0.71. Remove need to build with
 	-fcommon. Build with -W -Wall and without compiler warnings. Add some
 	compile time checks for structures that are written to tape and must
 	not change.

10.	Extensive regression tests. Every bug fixed by 0.4b48 release is now
 	covered by a regression test along with testing the restore of a historical
 	dump created by the previous versions from 0.4b5 through 0.4b47.

[Dump-announce] Dump/restore welcomes Tim Woodall as its new maintainer !

[Stelian P. <st...@po...>]

Hi everyone,

As you, the faithful users of dump/restore, have probably noticed, the 
project status has been on hiatus for the last months.

I am very happy that this situation is about to (happily) end, as Tim 
Woodall has stepped forward and suggested taking over this role.

Not only that, but he also has fixed many long standing bugs in the 
code, so I'm very confident that he is the perfect new maintainer for 
dump/restore.

I would also like to thank Mike for the work he has done on maintaining 
dump/restore for a few years.

Welcome Tim !

Stelian.

[Dump-announce] Dump/restore is looking for a new maintainer

[Stelian P. <st...@po...>]

Hello everybody,

It is probably obvious to all of you that I have been very silent
for some time now. The latest release of dump/restore was more than
3 years ago.

I should have written this announce long ago, but I guess it's not
easy to quit a project I have been working on for 15 years
(my first release of dump, 0.4b5, was released in September 1999 !).

I no longer have the time to work on dump anymore, and I'm not
sure dump as a tool still has a place in today's world. There are
die-hard admins who still use it, but maybe it's time for everybody
to move on.

Or not. Even if I don't really expect this to happen, maybe someone
will step up and take over the maintainership. Surprise me !

Dump's code is not the cleanest C code in the world (as a matter of
fact quite the opposite), but it is still interesting to study as it
was written in an age where code size and optimization meant something.
I did learn quite a few tricks from this code when I was a beginner
in programming, others could do as well.

I have long dreamed to re-write dump from scratch, keep the logic
and the tape format but throw away the historic dust. I'll leave
this on the TODO list for the new maintainer.

Thanks to everybody who sent patches, submitted bugs, posted on
the mailing lists, send me thank yous or complaints, or just simply
used dump/restore.

It has been fun.

Stelian.
-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b44 released

[Stelian P. <st...@po...>]

Hi everybody,

The 0.4b44 release of dump/restore has been published today,
incorporating a year-long list of bug fixes.

Thanks to all bug reporters and contributors.

Full changelog appended below.

Enjoy !

Stelian.

Changes between versions 0.4b43 and 0.4b44 (released June 10, 2011)
===================================================================

1.	Recognize ext4 partitions in dump -w commands (Sourceforge
	bug #3125587, RedHat bug #658890). Thanks to Jan Görig
	<jg...@us...> for reporting the bug and
	submitting the patch.

2.	Fix an issue with multi volume backups, which breaks
	restoring of files which are splitted on two or more
	volumes and are starting on 2nd tape or later (RedHat
	bug #507948).

3.	Fix a bug in dump when dumping files with holes. This bug
	was introduced in 0.4b42 while adding ext4 support.
	(Sourceforge bug #3133762).

4.	Fix a bug in restore -P where useless index files for compressed
	dumps were created (Debian bug #583093). Thanks to
	Mark Wooding <md...@di...> for the patch.

5.	Fix SYS_clone invocation on s390 architectures (Sourceforge
	bug #3303235). Thanks to Adam Tkac <at...@re...> for
	reporting the bug.

6.	Fix static builds. Thanks to Peter Volkov <pv...@ge...>
	for the patches.

7.	Fix false negatives in configure zlib test. Thanks to
	Bear Giles <bg...@co...> for the patch.

8.	Add quick regression script from Bear Giles <bg...@co...>.

9.	Fix a bug introduced in 0.4b43 causing restore to crash when
	asking for a new volume when doing multi-volume restores. Thanks
	to XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX for reporting the bug.

-- 
Stelian Pop <st...@po...>

Re: [Dump-announce] QFA tape position patch in latest Red Hat Rawhide

[Stelian P. <st...@po...>]

Hi Kenneth and List,

On Fri, Oct 29, 2010 at 11:24:40AM -0700, Kenneth Porter wrote:

> I just pulled down the latest SRPM from Rawhide to build and noticed it has 
> a patch for what I think might be a security-related bug, as I wasn't able 
> to see the bug matching the patch number in Red Hat's Bugzilla.
[...]

False alarm.

I have contacted the RedHat dump packager (Adam Tkac) which explained
to me that the bug is private because reported by a customer, and
that he fergot to send the patch upstream.

Quoting him:
"The patch fixes issue with multi volume backups. When you backup a
file which is splitted to two or more volumes and the file
starts on 2nd tape or later, then this file is not restored
correctly. With the patch file is restored correctly."

I will apply the patch in CVS ASAP, but I wanted to let all know
that there is no need to hurry to update, there are no security
implications here.

Thanks,

Stelian.
-- 
Stelian Pop <st...@po...>

[Dump-announce] QFA tape position patch in latest Red Hat Rawhide

[Kenneth P. <sh...@se...>]

I just pulled down the latest SRPM from Rawhide to build and noticed it has 
a patch for what I think might be a security-related bug, as I wasn't able 
to see the bug matching the patch number in Red Hat's Bugzilla.

You can grab the SRPM with the patch here:

<http://mirror.uoregon.edu/fedora/linux/development/source/SRPMS/dump-0.4-0.8.b43.fc14.src.rpm>

The patch is named dump-rh507948.patch.

[Dump-announce] Dump/restore 0.4b43 released

[Stelian P. <st...@po...>]

Hi everybody,

I've just published the 0.4b43 release of dump/restore on
sourceforge, incorporating all the changes that have been accumulating
in CVS since the last release (almost one year).

Once again, there are lots of changes in this new version, mainly
bug fixes and improvements for corner usage cases.

Full changelog appended below.

Enjoy !

Stelian.

Changes between versions 0.4b42 and 0.4b43 (released June 11, 2010)
===================================================================

1.	Fix a bug in dump making impossible to handle large toc files
	(> 2 GB). Thanks to X DUGi <xd...@us...> for
	reporting the bug (Sourceforge bug #2820629)

2.	Fix 'restore -x' in multi-volume mode, which caused files being
	spanned on the first and second volumes to be incorrectly extracted.
	Thanks to Adam Tkac <at...@re...> for reporting the bug.
	(there may be several bug reports about this issue, including
	Sourceforge bug #2117008, RedHat bugs #232415 and #444958).

3.	Remove -lselinux -lsepol from the standard libraries list,
	they shouldn't be needed if selinux is not enabled in dump
	(this also fixes a build failure when selinux libraries are
	not installed).

4.	Fix restoration of extended attributes of fifos and device nodes.
	Thanks to Igor Zhbanov <iz...@gm...> for the bug report.

5.	Don't attempt to set extended attributes on files that were not
	extracted in 'restore -N' mode. Thanks to Jan Görig
	<jg...@us...> for the patch.

6.	Make the dump man page explicit about ext4 support.

7.	Fix a bug in dump which caused EA entries to be unrecognizable by
	restore in some corner cases. Add a workaround to restore making
	it able to properly deal with those corrupted EA entries. Thanks
	to John Austin <jau...@us...> for reporting
	the bug.

8.	Fix some issues when restoring a dump which was generated using
	exclusion patterns (either via -e or via the nodump attribute)
	(see the Debian bug #574667 for details. Thanks to Frédéric
	Brière <fb...@fb...> for the bug report and the associated
	patch.

9.	Fix progress/estimated blocks display in dump when doing really
	huge backups. Thanks to Steve Bonds <sb...@us...>
	for the bug report and tests. (Sourceforge bug #2987758)

10.	Improve level 1 dump speed by rearanging the "mapdirs" code.
	Thanks to Andreas Kies <and...@t-...> for finding the
	bottleneck and sending a patch (Sourceforge bug #2998119).

11.	Use only ctime in order to compare newness instead of both
	ctime and mtime. This should both speed up dumping time and
	correct some side-effect bugs (like dumping files with an mtime
	in the future in every incremental backup). Thanks to
	Kieran Clancy <cod...@us...> for reporting the
	bug (Sourceforge bug #2999207).

12.	Extract dumped UNIX sockets instead of ignoring them.
	(Sourceforge bug #3007216).

13.	Compiler warning fixes (mainly warn_unused_result ones).

-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b42 released

[Stelian P. <st...@po...>]

[Actually I did the release last Thursday, but fergot to announce it here...]

Hi everybody,

I finally got the time to release a new version of dump/restore,
incorporating all the changes that have been accumulating in CVS
for 3.5 years !

There are lots of changes in this new version (mainly bug fixes and
small improvements). I've even included a patch from Gertjan van Wingerde
which should add ext4 support (I have not personnaly tested this, so be
careful !).

Full changelog appended below.

Enjoy !

Stelian.

Changes between versions 0.4b41 and 0.4b42 (released June 18, 2009)
===================================================================

1.	Fix printout of the 'Connection to' message in dump/restore.
	Thanks to Dale Wiles <dw...@us...> for the
	bug report and its fix.

2.	Fix dump -w/-W output for filesystems having the last backup
	level equal to 0. Thanks to Pascal Bouchareine
	<ka...@us...> for reporting the bug.

3.	Enable restore to handle restoring onto a different SELinux
	policy from the dump. Thanks to Tony Nelson 
	<ton...@us...> for the patch.
	(see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189845
	for details)

4.	Fix EA set failures when restoring immutable files. Thanks
	to Andrew Kroeger for the patch.

5.	Fix "mode file too large" errors when restoring huge backups.
	Thanks to Kenneth Porter <sh...@se...> for the bug
	report.

6.	Add the ability to link against libtinfo library if present,
	instead of libtermcap or libncurses libraries. Thanks to
	Adam Tkac <at...@re...> for the patch.

7.	When comparing a backup, do not consider to be an error the fact
	that we encounter files created while dump was in progress.
	Thanks to Kenneth Porter <sh...@se...> for the bug
	report.

8.	Force '-a' to be the default value when running 'restore -C'.
	Thanks to Kenneth Porter <sh...@se...> for the bug
	report.

9.	Many improvements to the 'cron_dump_to_disk' example.
	Thanks to Aaron S. Hawley <ash...@us...> for
	the patch.

10.	Fix the QFA generation when extended attributes are backuped
	along with the inodes. Prior to this fix, the entries for
	some inodes may get corrupted (duplicated entries or incorrect
	ones), making the QFA file unusable for repositionning in
	restore. Many thanks to Kenneth Porter <sh...@se...>
	for the bug report and the testing of the fix.

11.	Fix EA restoration in debug mode (Sourceforge bug #1986216).

12.	Stefan Auracher <st...@on...> noticed that the Tower
	of Hanoi backup strategy documented in the man page wasn't
	actually based on the Tower of Hanoi algorithm. The man page
	was updated accordingly.

13.	Fix missing level information from dump output when using
	the default level (RedHat bug #493635). Thanks to Adam Tkac
	<at...@re...> for the patch.

14.	Fix the dump man page to reflect the fact that the default
	dump level is 0 not 9 (RedHat bug #356121). Thanks to Adam Tkac
	<at...@re...> for the patch.

15.	Fixed a few spelling errors in the man pages (RedHat bug #489853).
	Thanks to Adam Tkac <at...@re...> for the patch.

16.	Fixed restore man page and program usage which incorrectly stated
	that -P and -A were both allowed in the same invocation (RedHat
	bug #490627). Thanks to Adam Tkac <at...@re...> for the patch.

17.	Use sys_clone under Linux to share I/O contexts between dump
	processes, thus drastically increasing the performance of dump
	under CFQ (which is the default I/O scheduler used in a number of
	distributions). Thanks to Jeff Moyer <jm...@re...> for the
	patch.

18.	Add (preliminary) ext4 support - thanks to libext2fs which does
	all the job for us. Thanks to Gertjan van Wingerde
	<gwi...@gm...> for the patch.

-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b41 released.

[Stelian P. <st...@po...>]

Hi everybody and Happy New Year !

A new version of dump/restore, the Linux ext2/ext3 filesystem
backup utilities, has been released today.

This is a maintenance release fixing a few bugs in dump and restore, see
the attached changelog for full details.

You can download the new version at dump/restore's homepage:  
        http://dump.sourceforge.net
                   
Enjoy,
    
Stelian.

Changes between versions 0.4b40 and 0.4b41 (released January 2, 2006)
=====================================================================

1.      Fix restore of dumped Access Control Lists. The previous
        code for EA works fine, but ACLs needed conversion from the
        ext2/3 disk format to posix_acl format before restoring.

2.      Fix some issues with restoration of EA on big endian
        platforms.

3.      Fix restore when the symtab is over 2GB in size.

4.      Made the directory hash indexing an optional feature,
        accessible by the '-H' option of restore, and disable it
        by default.

5.      Fixed dump to not include extended attributes information
        in the toc (archive) file which confused restore -t.


-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b40 released.

[Stelian P. <st...@po...>]

Hi everybody,

A new version of dump/restore, the Linux ext2/ext3 filesystem backup
utilities has been released today.

This release features a few bug fixes and support for ext2/ext3
extended attributes (EA). For additionnal details, see the full
ChangeLog below.

You can download the new version at dump/restore's homepage:
	http://dump.sourceforge.net

Enjoy,

Stelian.

Changes between versions 0.4b39 and 0.4b40 (released May 2, 2005)
=================================================================

1.	Changed restore to emit warnings (instead of emitting a fatal
	error) if a file (or a directory) is unavailable for a 
	comparision (if the user doesn't have the necessary permissions
	to access it for example). Thanks to Kenneth Porter
	<sh...@se...> for the bug report.

2.	Re-done the 'do not save directory entries to non-dumped inodes
	(excluded from dump)' feature. The previous implementation
	worked well for excluded directories but not for regular files.
	Thanks to Kenneth Porter <sh...@se...> for the bug
	report.

3.	Fixed a bug in dump where the tape size was miscalculated when
	the user used -d/-s to specify the tape characteristics. Thanks
	to Philip Goisman <go...@ph...> for reporting
	the bug.

4.	Fixed another bug introduced in restore with the hashtree
	implementation. This one caused restore to stop saying
	"removenode: non-empty directory" in some cases.

5.	Added support for dumping and restoring ext2/3 extended
	attributes (EA), like the access control lists (ACL) or
	the security labels used by SELinux.
-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b39 released.

[Stelian P. <st...@po...>]

Hi all.

A new version of dump/restore, the Linux ext2/ext3 filesystem
backup utilities, has been released today.

This release fixes a serious bug in 'restore -C' introduced by
the previous (0.4b38) version, bug which could lead to data 
modification on the filesystem being compared to the dump.

Some other minor fixes are included in this release, for full
details see the ChangeLog below.

The next version of dump/restore will feature EA/ACL support, and
there is already a beta patch implementing this. If you use EA/ACLs,
please do test this patch and report back (get the patch from dump's
homepage).

The dump/restore homepage is located at:
	http://dump.sourceforge.net

Stelian.

Changes between versions 0.4b38 and 0.4b39 (released January 21, 2005)
======================================================================

1.	The newly added dump_on_cd_3 example was buggy, replace it
	with an updated version from Andrew Basterfield
	<bo...@ce...>.

2.	Made restore to chdir() back into the initial directory when
	dumping core while aborting a comparision operation. The
	previous behaviour was to write the corefile at the root of
	the directory being compared, which could very well be 
	read only and preventing the corefile generation. Thanks
	to Kenneth Porter <sh...@se...> for the bug report.

3.	Silenced the failure to call fgetflags() when comparing an
	entry which has no ext2 attributes (as in lsattr()).

4.	Fix a brown paper bug in restore -C which broke restore and
	caused modifications on the filesystem being compared
	(directories containing a file with the same name as the
	directory get renamed to RSTTMP...). Thanks to Kenneth Porter
	<sh...@se...> for finding the bug and helping me
	reproduce it.

5.	Made restore -C force the -N flag (no writing allowed on
	the disk) in order to prevent more bugs like the above one.
-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b38 released.

[Stelian P. <st...@po...>]

Hi everybody.

A new version of of dump/restore, the Linux ext2/ext3 filesystem
backup utilities, has been released today.

This release features several small bug fixes and a number of
performance enhancements, see the full ChangeLog below for full
details.  
 
The next version of dump/restore will feature EA/ACL support, and
there is already a beta patch implementing this. If you use EA/ACLs,
please do test this patch and report back (get the patch from dump's
homepage).

The dump/restore's homepage is located at:
	http://dump.sourceforge.net

Happy new year !

Stelian.

Changes between versions 0.4b37 and 0.4b38 (released January 7, 2005)
=====================================================================

1.	Fix a couple of troff syntax bugs in the man pages.
	Thanks to Eric Raymond <es...@th...> for the patch.

2.	Made restore use either libncurses or libtermcap, depending
	on which one is available at configure time.

3.	Fixed restore negative size display bug when comparing a
	dump containing files over 2GB. Thanks to Steve Bonds
	<sb...@us...> for the bug report.

4.	Do not save directory entries to non-dumped inodes 
	(excluded from dump). This will eliminate the 'missing
	file' warnings when doing 'restore -C'.

5.	Fix dump crash when backuping a huge (2TB) filesystem,
	due to a bogus calculation on the inode map size.
	Thanks to Kevin B. Haines <K.B...@rl...> for 
	submitting the bug and testing the fix.

6.	Fix a problem in restore where the final \0 in the symbolic
	link names could have been lost, generating corrupt filenames.
	Thanks to Kyle Wilson <kyl...@am...> for reporting the
	bug.

7.	Implemented a hash list for the directory names in restore.
	The linear list used before caused problems in interactive
	restores when dealing with directories having thousands of
	entries. Thanks to Brian Ristuccia <bri...@st...>
	for reporting the bug.

8.	Improved restore -C, this time including the directory
	attributes into the comparision.

9.	Made restore understand tapes containing EA/ACLs (which will
	be dumped by the next version of dump). In this version 
	extended attributes on the tape are ignored, for full EA/ACL
	support wait for the next version or try the experimental EA
	patch.
-- 
Stelian Pop <st...@po...>    

[Dump-announce] preliminary EA/ACL support in dump/restore

[Stelian P. <st...@po...>]

Hi everybody.

Support of ACLs is a feature requested by many for a long time and I
finally got the time to implement it. Since on Linux ACLs are only
a particular case of EAs (Extended Attributes), I implemented full
EA support, meaning that even security labels set (for example) by
SELinux will be backuped.

You can download a patch (against the current CVS dump) here:
	http://dump.sourceforge.net/dump-ea.patch.bz2

Some notes:
	* the patch is complete, meaning that everything is supposed to 
	  work: dumping, extraction, comparing, in all modes etc.

	* the patch modifies some key areas of restore, so pay
	  attention and verify that you can reread your backups
	  before relying on them.

	* the tape format changed a bit and you will need the patched
	  restore to extract the files.(*)

Please test this and report back if there are any issues. 

I plan to release a new version of dump (0.4b38) in the next few
days, but I will NOT include the EA patch in it, because it really
needs more testing.

But as soon as I get enough positive replies on the EA patch
I will include it in the official mainline.

Thanks,

Stelian.
	  
(*) In fact is a bit more complicated:
- if no EAs are backuped, dump format should remain the same as in
  the old versions, so you can use whatever restore you want.
- if EAs are backuped but never on directory inodes, then a reasonable
  recent version of restore should be happy and just skip over the
  extended attributes data.
- if EAs are backuped for directory inodes, older restores will fail
  to extract with some 'directory corrupted' error.

-- 
Stelian Pop <st...@po...>    

[Dump-announce] Dump/restore 0.4b37 released.

[Stelian P. <st...@po...>]

Hi everybody,

A new version of of dump/restore, the Linux ext2/ext3 filesystem
backup utilities, has been released today.

This release fixes a serious bug in dump, where a filesystem offset
could have been miscalculated on large filesystems, leading to
"bread lseek errors".

Some other minor fixes/features made it also in this new release,
see the ChangeLog below for full details.

You can download the new version at dump/restore's homepage:  
	http://dump.sourceforge.net
		   
Enjoy,
    
Stelian.

Changes between versions 0.4b36 and 0.4b37 (released July 7, 2004)
==================================================================

1.	Added the --enable-staticz configure option which enables
	dump and restore to be linked with static versions of
	libz and libbz2 (and dynamic versions of all other libraries).
	This will make Debian users happy, because libz and libbz2
	were the only needed libraries living in /usr, all the
	others live in /lib. In case of system emergency, it is 
	better not to have to rely on an extra filesystem.
	Thanks to Bdale Garbee <bd...@ga...> for the suggestion.

2.	Fix compilation on (at least the Linux Debian port to) AMD64.
	(<ext2fs/ext2_types.h> defines some types (__s64 and __u64)
	that are also defined by <linux/types.h> (<asm/types.h>) and 
	they conflict).

3.	Make dump's reading of the dumpdates file a bit more robust,
	preventing dump from crashing when the dumpdates file has
	been modified by hand.

4.	Fixed some offset calculations in dump code which could 
	lead to "bread lseek errors" on large filesystems. Thanks
	to Bruce Lowekamp <low...@us...> for
	reporting this bug and debugging the issue.

5.	Made dump use the blkid library when searching for devices
	by label or uuid instead of dump's own routines.

6.	Corrected a bug in dump where a wrong LABEL=... line in
	/etc/fstab could prevent dump from dumping unrelated 
	filesystems. Thanks to Bruce Lowekamp
	<low...@us...> for reporting the bug.

-- 
Stelian Pop <st...@po...>    

[Dump-announce] Dump/restore 0.4b36 released

[Stelian P. <st...@po...>]

Hi everybody,

A new version of dump/restore, the Linux ext2/ext3 filesystem
backup utilities, has been released today.

This release features some interoperability fixes (make restore
understand Solaris 7 ufsdump and FreeBSD UFS2 tapes), some new 
features (specify different tape sizes for each tape when doing
multi-volume dumps, extend dump to understand unlimited dump 
levels) and some other miscellaneous fixes.

You can download the new version at dump/restore's homepage:  
        http://dump.sourceforge.net

Enjoy,

Stelian.

Changes between versions 0.4b35 and 0.4b36 (released April 21, 2004)
====================================================================

1.	Fixed dump compilation with old gcc versions. Thanks to
	Mike Castle <da...@us...> for the patch.

2.	Fixed some warnings (howmany, roundup, powerof2 redefined)
	when compiling against a recent glibc version.

3.	Fixed a bug in restore preventing the read of a dump tape
	written with Solaris 7 ufsdump. Thanks to Patrick Higgins
	<phi...@tr...> for reporting the bug and providing 
	the test case.

4.	Changed dump to enable the creation of volumes of different
	sizes in a single run (make -B accept a list of values).
	Patch contributed by Florian Zumbiehl <fl...@gm...>.

5.	Use the glibc provided minor() and major() macros instead
	of our own bitmask implementation. This should be safe for
	when the major/minor namespace will migrate to 32 bits.
	Thanks to Zhang Jun <zha...@na...> for reporting
	the bug.

6.	Made explicit in the dump man page that dump will not create
	a remote file, it will only write to an already existing one.

7.	Another try at making size estimates better again.

8.	Put back the inconditional running of the end-of-tape
	script which was changed in 0.434 to be run only when -M
	or multiple -f were NOT specified. Some users rely on this
	feature even when it is combined with -M/-f.

9.	Fixed restore when restoring huge backups (where rstdir...
	temporary files are over 2GB). Thanks to 
	Raphael Jaffey <rj...@ar...> for reporting this, 
	debugging the issue and making the patch.

10.	Made restore understand FreeBSD UFS2 tapes. Thanks to
	David <vr...@us...> for submitting the bug
	and providing a test case.

11.	Made dump work with an arbitrary integer level (no more 10
	levels only limitation). Thanks to Matthew
	<msv...@mi...> for the patch.
	

-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b35 released

[Stelian P. <st...@po...>]

Hi everybody,

A new version of dump/restore, the Linux ext2/ext3 filesystem
backup utilities, has been released today.

This is a maintenance release containing a few bug fixes (build fixes
for 64 bit platforms, man page clarifications) and additions 
(possibility to exclude an unlimited number of inodes, make restore
build on Solaris, make QFA work both on local and remote tapes).
See the full changelog below for more details.

You can download the new version at dump/restore's homepage:
        http://dump.sourceforge.net

Enjoy,

Stelian.

Changes between versions 0.4b34 and 0.4b35 (released December 21, 2003)
=======================================================================

1.	Added a note in the dump man page saying that the default
	blocksize can be 32 if -d is used with a high density argument.
	Thanks to Antonios Christofides (A.C...@it...)
	for the patch.

2.	Fixed configure to correctly understand CPPFLAGS, CFLAGS,
	LDFLAGS environment variables. Thanks to Arcady Genkin
	(ant...@us...) for reporting the bug.

3.	Made -e/-E options of dump accept an unlimited number of inodes
	to be excluded, rather than a hardcoded maximum. Thanks to 
	Dietrich Rothe (d-...@us...) for the patch.

4.	Updated the autoconf system to 2.50. Forced the -D_BSD_SOURCE
	and -D_USE_BSD_SIGNAL defines in configure in order to solve
	64bit build problems because quad_t is redifined with a 
	different signature. Thanks to Mike Harris (mh...@re...)
	for reporting this bug.

5.	Made restore build on Solaris, making possible to
	restore Linux's "enhanced" tapes. Thanks to Uwe Gohlke
	(uw...@ug...) for the patch.

6.	Made an extension in the dump tape format capable of saving
	MacOSX specific inode extensions. Uwe Gohlke (uw...@ug...)
	wrote the extension and contributed the restore code back
	into this codebase. The same extension mechanism will be
	used in the future to save ACLs...

7.	Made rmt work correctly with regard to QFA and local/remote
	files and tapes. The remote access will however work only 
	when the dump provided rmt version is used. If you want to
	use another rmt server, please do not use the QFA feature.
	Thanks to Uwe Gohlke (uw...@ug...) for the patch.

-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b34 released

[Stelian P. <st...@po...>]

Hi,

A new version of dump/restore, the ext2/ext3 Linux filesystem
backup utilities, has been released today.

Starting with this release, the dump/restore code has been 
relicenced under the 'revised' BSD licence, as per
ftp://ftp.cs.berkeley.edu/ucb/4bsd/README.Impt.License.Change.

A couple of new features made it into this release (LZO fast
compression, new extended rmt capable of encryption, make dump work
with 2.5 kernel EOT semantics) and a LOT of small bugfixes.

The dump/restore homepage is located at:
        http://dump.sourceforge.net

The full changelog is appended below.

Enjoy !

Stelian.

Changes between versions 0.4b33 and 0.4b34 (released April 18, 2003)
====================================================================

1.	Fixed the INSTALL file to reflect the actual install paths.
	Thanks to David Ronis <ro...@ro...> for
	reporting the bug.

2.	Fixed the configure script to only check for headers presence
	instead of trying to compile them. This should fix issues
	with old build environments. Thanks to Kari Lempiainen 
	<ka...@fu...> for reporting the bug.

3.	Fixed restore to correctly ignore sockets when comparing
	a dump (as socket cannot be properly restored anyway). Thanks
	to Gunther Reiszig <gu...@mi...> for reporting the bug.

4.	Fixed restore to correctly access the archive file (-A argument)
	even when using a remote tape. Thanks to Fabrice Bellet 
	<fa...@be...> for reporting the bug.

5.	Fixed (again) handling of long (largefile) seeks in rmt.
	Thanks to Fabrice Bellet <fa...@be...> for reporting
	the bug.

6.	Fixed restore corner case when dealing with large block sizes
	dump is able to write now (-b 1024). Thanks to Fabrice Bellet
	<fa...@be...> for reporting the bug.

7.	Fixed a bug preventing dump to access a filesystem having 
	a label exactly 16 bytes in length. Thanks to <mi...@ti...>
	for reporting the bug.

8.	Made dump store dump dates using explicit timezones, fixing a
	problem with incremental dumps if the timezone is modified 
	between the dumps. Thanks to Philippe Troin <ph...@fi...> for
	the bug report and the patch.

9.	Fixed a bug encountered when dumping individual files (not full
	filesystems or directories) and dangling symbolic links happen
	to be in the list of files. For as far as dump is concerned,
	dangling symbolic links are allowed, and are dumped as is.
	Thanks to Jin-su Ahn <js...@ee...> for reporting the
	bug and providing the fix.

10.	Fixed open and creation modes and permissions for QFA and
	table-of-contents files in dump and restore. Thanks to 
	Philippe Troin <ph...@fi...> for the patch.

11.	Fixed the archive file descriptor handling enabling it to be 0.
	This can happen in some cases when shell redirections are used.
	Thanks to Philippe Troin <ph...@fi...> for the patch.

12.	Delayed the opening of archive file until after suid had been
	dropped (fixing a possible security issue if dump is suid). 
	Thanks to Philippe Troin <ph...@fi...> for the patch.

13.	Fixed the 'S' command handling in the rmt client part.
	Thanks to Philippe Troin <ph...@fi...> for the patch.
	
14.	Modified the end-of-tape script handling to print out statistics
	(and stop the timer) before launching the eot script. Also, the eot
	script does not get run anymore when using -M (which makes sense) or
	when multiple tapes are listed on the command line 
	(-f tape0,tape1,tapen) (which also makes sense).
	Thanks to Philippe Troin <ph...@fi...> for the patch.

15.	Relicensed dump/restore under the 'revised' BSD license, as per
	ftp://ftp.cs.berkeley.edu/ucb/4bsd/README.Impt.License.Change.

16.	Added LZO compression to dump. This new compression method has
	the advantage of being super fast, thus not killing tape streaming
	on slow machines. Thanks to Helmut Jarausch 
	<jar...@ig...> for the patch and to 
	Markus Oberhumer <ma...@ob...> for giving special permission
	to include his miniLZO project (GPL licensed) in dump/restore.

17.	Some small buffer overruns fixes in rmt. Thanks to Antonomasia
	<an...@no...> for reporting the bugs.

18.	Added a special rmt version which can do encryption when writing
	to tape. Read examples/encrypted_rmt/README for details on
	how to enable and configure it. Thanks to Ken Lalonde
	<ke...@gl...> for the patch.

19.	Made dump work with 2.5 kernel end of tape early warning semantics.
	Thanks to Kai Makisara <Kai...@ko...> for the patch.

20.	Fixed a bug which caused dump -w|-W not to work anymore, because
	the fs_freq and fs_passno fields in /etc/mtab are always set
	to 0 0. Thanks to Trent Piepho <xy...@sp...> for 
	reporting the bug.


-- 
Stelian Pop <st...@po...>

[Dump-announce] dump/restore relicensing

[Stelian P. <st...@po...>]

Hi everybody,

I have relicensed the dump/restore code (in CVS now, will be
effective when the next release will go out) under the 'revised'
BSD license (the advertising clause removed).

The statement from the University of Berkeley, giving permission
do to so on any code being copyrighted by the USB is here:
	ftp://ftp.cs.berkeley.edu/ucb/4bsd/README.Impt.License.Change

The new relicense should solve some problems, including the
incompatibility with the GPL license, while not hurting anyone or
anything. Read more about this at:
	http://www.gnu.org/philosophy/bsd.html

If somebody is opposed to this license change and owns a copyright
on some part of dump/restore source please contact me ASAP. 

Thanks,

Stelian.
-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b33 released

[Stelian P. <st...@po...>]

Hi everybody,

A new version of dump/restore, the Linux ext2/ext3 filesystem
backup utilities, has been released today.

This release features several bugfixes (fixed the endianness issues
with compressed tapes, made rmt understand largefiles seeks, fixed
the build with ancient versions of libext2fs) and some new and useful
enhancements (let the user pass the dumpdates path on the dump command
line, made dump look into /etc/mtab and /etc/fstab for filesystems to 
dump etc). See the changelog below for full details. 

You can download the new version at dump/restore's homepage:
	http://dump.sourceforge.net

Enjoy,

Stelian.

Changes between versions 0.4b32 and 0.4b33 (released February 10, 2003)
=======================================================================

1.	Added a note in the restore man page clarifying the question
	'set the permissions on the current directory ?' asked by
	restore at the end of treatment in -i and -x modes.

2.	Fixed the endianess issues when reading compressed tapes.
	Thanks to Dark Force <da...@us...> for
	reporting this bug and providing test cases.

3.	Fixed the "ACL won't be dumped" warning message (which showed
	an extra, unrelated error message). Thanks to Dragan Krnic
	<dk...@ly...> for reporting this bug.

4.	Made dump look first into /etc/mtab, then into /etc/fstab 
	when searching for filesystem paths. Also fixed some problems
	caused by binding mounts or multiple block device mounts.
	Thanks to Matus Uhlar <uh...@fa...>, Elliott Mitchell
	<eh...@m5...>, Greg Edwards <ged...@us...>,
	Brian Hoy <bri...@op...>. (fixes Debian bugs #147086
	and #160305, Sourceforge bugs #618699 and #679832).

5.	Made dump's -I option accept the value '0' meaning all the
	read errors will be ignored. This can be useful when running
	dump from unattended sessions (like cron jobs). Thanks to
	John I Wang <ji...@us...> for the suggestion.

6.	Fixed the output of dump to indicate 'blocks' instead of
	'tape blocks' in the various messages (blocks are always
	1 Kilobyte, tape blocks are 1 BK * '-b' argument), and 
	made it clearly print the current blocksize at the start of
	a dump. Thanks to Michal Szymanski <ms...@as...> for
	the suggestions.

7.	Made rmt understand long (largefiles) seeks.

8.	Fixed build with very old versions of libext2fs, where
	EXT2_FT_* constants were undefined.

9.	Made dump accept the dumpdates path on the command line
	(-D file option) instead of using only the hardcoded one.
	Thanks to Piete Brooks <pb...@us...> for the
	suggestion.

10.	Enabled rmt, LFS, readline, QFA options by default in
	./configure. Updated the configure process (new versions
	of config.guess, config.sub etc).

-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b32 released

[Stelian P. <st...@po...>]

Hi everybody,

A new version of dump/restore, the Linux ext2/ext3 filesystem
backup utilities, has been released today.

This new release features several minor and not so minor bugfixes.
For details, read the changelog, pasted below.

As you all already know it, the dump/restore homepage is located at:
	http://dump.sourceforge.net

Enjoy,

Stelian.

Changes between versions 0.4b31 and 0.4b32 (released November 15, 2002)
=======================================================================

1.	Changed dump to use fcntl(F_SETLK) style locking instead
	of flock() when locking the dumpdates file. With the old 
	locking scheme, a local user having read rights on the 
	dumpdates file could be able to do a Denial of Service attack
	on dump. In order to lock the dumpdates file with the new
	scheme, the user would need to have write access on the file.
	Thanks to Richard Johnson <Ric...@ey...> for 
	reporting the bug (originally a bugtraq post).

2.	Fixed interactive 'ls' which caused spurious errors warnings
	about 'undefined filetypes' detected. Thanks to Jorgen Ostling 
	<jor...@us...> for reporting this 
	bug.

3.	Fixed dump's estimate when dealing with sparse inodes.

4.	Modified dump to allow setting a blocksize bigger than 32kB
	(raised the limit to 1024kB), because newer hardware needs
	this for proper operation. Thanks to Dirk Traenapp
	<dtr...@us...> for reporting this.

5.	Fixed a bug causing Dump to stop and report an error if an
	inode number in the exclude file was followed by some amount
	of whitespace. Thanks to Jeffrey Sofferin 
	<sof...@us...> for reporting this bug.

6.	Fixed a bug which caused restore, in some particular cases,
	to ask some 'scary' questions and leave a bunch of RSTTMP
	directories behind when restoring incremental tapes. Thanks
	to Philippe Troin <ph...@fi...> for reporting this bug and
	providing the test cases.

7.	Changed the wording when inodes are excluded from dump:
	replaced 'Added inode 7 to exclude list' with
	'Excluding inode 7 (resize inode) from dump', as suggested
	by Elliott Mitchell <eh...@m5...> in a Debian bug report.

-- 
Stelian Pop <st...@po...>

[Dump-announce] Dump/restore 0.4b31 released

[Stelian P. <st...@po...>]

Hi everyone,

A new version of dump/restore, the Linux ext2/ext3 filesystem backup
utilities, has been released today.

This release fixes a bug (introduced with 0.4b29) which prevented the
use of a remote tape drive. Since it is a pretty important bug, and
I will not be very available in August (holidays), I'm releasing 
the fix immediately.

Enjoy !

Stelian.

Changes between versions 0.4b30 and 0.4b31 (released July 30, 2002)
===================================================================

1.      Fixed rmt open flags transmission (GNU's symbolic syntax over
        rmt) which I broke in 0.4b29. Thanks to Eros Albertazzi
        <er...@la...> for reporting the bug.

-- 
Stelian Pop <st...@po...>