Fix an issue with the size of dump maps appearing when the filesystem has been resize...

[dump.git] / KNOWNBUGS

diff --git a/KNOWNBUGS b/KNOWNBUGS
index 4776dca85d3b5b49a87870d64edf6ebf3df991a9..e79ded9e72bb33ea5816010c611f0140113a33f2 100644 (file)
--- a/KNOWNBUGS
+++ b/KNOWNBUGS
@@ -1,15 +1,17 @@
+$Id: KNOWNBUGS,v 1.5 1999/11/21 00:17:12 tiniou Exp $
+
 Known bugs and limitations of the dump/restore port
 ===================================================
 
-1.     Multi-volume does not work: restore does not succeeds in
-       resynchronizing itself on a multi-volume dump.  Thus, some files are
-       not restored.
-
-       Update: this is fixed in 4.0b5, needs succes reports!
-
-2.     I have tried to minimize changes in the BSD source and some parts
+1.     I have tried to minimize changes in the BSD source and some parts
        may look ugly.  dump/tape.c is really awfull but this is pure BSD
        code :-)  Maybe, I should replace it with a simpler and cleaner
        version.
 
-3.     Kerberos mode is _NOT_ tested.
+2.     Kerberos mode is _NOT_ tested.
+
+3.     Some users related possible problems when dumping
+       active (mounted) filesystems. The problems are reported as
+       lseek and read error messages (with a negative count). If
+       you encounter this kind of problems, please report them
+       to the author.