Made dump report the number of blocks dumped per volume.

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 5d690aa6c474e78bc0779c2441923403c5b82fdc..f603acafa33d01675f6bd1eef3d3401d49c6e2d9 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,13 @@
-$Id: CHANGES,v 1.92 2000/11/30 09:53:10 stelian Exp $
+$Id: CHANGES,v 1.101 2001/02/16 10:40:47 stelian Exp $

 
 

-Changes between versions 0.4b20 and 0.4b21 (released ?????????????????)
-=======================================================================
+Changes between versions 0.4b21 and 0.4b22 (released ????????????????)
+======================================================================
+
+1.     Let dump report the number of blocks dumped per volume.
+       Thanks to Kenneth Porter <shiva@well.com> for the suggestion.
+
+Changes between versions 0.4b20 and 0.4b21 (released January 13, 2001)
+======================================================================

 
 1.     Fixed some bugs in the dump -w|-W logic introduced by
        the previous version. Thanks to Andreas Dilger 
 
 1.     Fixed some bugs in the dump -w|-W logic introduced by
        the previous version. Thanks to Andreas Dilger 


@@ -11,6 +17,44 @@ Changes between versions 0.4b20 and 0.4b21 (released ?????????????????)
        headers (filesystem label related). Thanks to many users
        who reported this stupid error.
 
        headers (filesystem label related). Thanks to many users
        who reported this stupid error.
 

+3.     Fixed a build problem on old lib5 based systems dealing with 
+       _PATH_MNTTAB being undefined. Thanks to John Adams
+       <johna@onevista.com> for reporting the bug.
+
+4.     Improved the error detection in restore when creating
+       the temporary files in TMPDIR. Now restore will corectly
+       report a 'no space left on device' error instead of 
+       strange errors which could imply an archive corruption.
+       Thanks to Gabriel Somlo <somlo@cs.colostate.edu> and
+       bgjenero <bgjenero@sympatico.ca> for reporting the bug.
+
+5.     Added the throughput information in dump's progression
+       messages.  Thanks to Andreas Dilger <adilger@turbolinux.com> 
+       for the patch.
+
+6.     Use libext2fs's inode scanning routines, which are particularly
+       robust when dealing with errors (especially when having some
+       bad blocks on the filesystem). Many thanks to Colin
+       <colin@horizon.com> for reporting the bug, investigating
+       the issues, finding a workaround, writing the patch and
+       fully testing it... (of course, if this patch will break
+       anything, he is to blame for :-)).
+
+7.     Made dump and restore LFS aware. Dump can dump a filesystem
+       containing large files, generate a large file on output and
+       restore can restore them. This feature is not enabled by
+       default, use --enable-largefile option of configure to enable
+       it (you need to have a LFS aware glibc though). Thanks to
+       Andrea Arcangeli <andrea@suse.de> for submitting the patch,
+       and to Theodore T'so <tytso@valinux.com> for his always
+       useful thoughts.
+
+8.     Made dump ask upon a tape write error if it should rewrite
+       the current volume (assume this is a bad tape) or if it should
+       assume an end-of-tape condition (useful for tape drives which
+       behaves badly at the end of the tape). Thanks to Andreas
+       Dilger <adilger@turbolinux.com> for the suggestion.
+

 Changes between versions 0.4b19 and 0.4b20 (released November 10, 2000)
 =======================================================================
 
 Changes between versions 0.4b19 and 0.4b20 (released November 10, 2000)
 =======================================================================