Fix SIGSEGV in dump when dumping huge 2TB filesystems (bad inode map calculation)

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index f71dc06943669fed74e7a607f93cd6612dc551a0..5ae2f0a8f994b646c7d9ad3589abac5e6ccab20b 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.256 2004/07/20 15:52:58 stelian Exp $
+$Id: CHANGES,v 1.259 2004/11/22 10:32:31 stelian Exp $
 
 Changes between versions 0.4b37 and 0.4b38 (released ????????????)
 ==================================================================
@@ -9,6 +9,19 @@ Changes between versions 0.4b37 and 0.4b38 (released ????????????)
 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
+       <sbonds@users.sourceforge.net> 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.Haines@rl.ac.uk> for 
+       submitting the bug and testing the fix.
+
 Changes between versions 0.4b36 and 0.4b37 (released July 7, 2004)
 ==================================================================