Let the user give the dumpdates path as an argument to dump (-D)

[dump.git] / dump / dump.8.in

diff --git a/dump/dump.8.in b/dump/dump.8.in
index c92f90c3268dc512df280c3c152b2b74569efa31..b44970148d47214832d8053fbcc36314f49704bb 100644 (file)
--- a/dump/dump.8.in
+++ b/dump/dump.8.in
@@ -30,7 +30,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"

-.\"    $Id: dump.8.in,v 1.44 2002/07/24 14:12:00 stelian Exp $
+.\"    $Id: dump.8.in,v 1.48 2003/01/21 10:42:27 stelian Exp $

 .\"
 .TH DUMP 8 "version __VERSION__ of __DATE__" BSD "System management commands"
 .SH NAME
 .\"
 .TH DUMP 8 "version __VERSION__ of __DATE__" BSD "System management commands"
 .SH NAME


@@ -42,6 +42,7 @@ dump \- ext2/3 filesystem backup
 [\fB\-B \fIrecords\fR]
 [\fB\-b \fIblocksize\fR]
 [\fB\-d \fIdensity\fR]
 [\fB\-B \fIrecords\fR]
 [\fB\-b \fIblocksize\fR]
 [\fB\-d \fIdensity\fR]

+[\fB\-D \fIfile\fR]

 [\fB\-e \fIinode numbers\fR]
 [\fB\-E \fIfile\fR]
 [\fB\-f \fIfile\fR]
 [\fB\-e \fIinode numbers\fR]
 [\fB\-E \fIfile\fR]
 [\fB\-f \fIfile\fR]


@@ -115,17 +116,16 @@ to be used by
 to determine whether a file is in the dump file that is being restored.
 .TP
 .BI \-b " blocksize"
 to determine whether a file is in the dump file that is being restored.
 .TP
 .BI \-b " blocksize"

-The number of kilobytes per dump record. Since the IO system slices all
-requests into chunks of 
+The number of kilobytes per dump record. The default blocksize is 10
+and the maximal value is 1024.
+Note however that, since the IO system slices all requests into chunks
+of 

 .B MAXBSIZE
 .B MAXBSIZE

-(typically 64kB), it is not possible to use a larger blocksize without having 
-problems later with
-.BR restore (8).
-Therefore
-.B dump
-will constrain writes to 
-.B MAXBSIZE.
-The default blocksize is 10.
+(which can be as low as 64kB), you can experience problems with
+.BR dump (8)
+and
+.BR restore (8)
+when using a higher value, depending on your kernel and/or libC versions.

 .TP
 .BI \-B " records"
 The number of 1 kB blocks per volume. Not normally required, as
 .TP
 .BI \-B " records"
 The number of 1 kB blocks per volume. Not normally required, as


@@ -147,6 +147,11 @@ Set tape density to
 The default is 1600BPI. Specifying a tape density overrides the end-of-media
 detection.
 .TP
 The default is 1600BPI. Specifying a tape density overrides the end-of-media
 detection.
 .TP

+.BI \-D " file"
+Set the path name of the file storing the information about the previous 
+full and incremental dumps. The default location is
+.IR __DUMPDATES__ .
+.TP

 .BI \-e " inodes"
 Exclude 
 .I inodes
 .BI \-e " inodes"
 Exclude 
 .I inodes


@@ -192,8 +197,9 @@ this can be overridden by the environment variable
 .BR RMT .
 .TP
 .BI \-F " script"
 .BR RMT .
 .TP
 .BI \-F " script"

-Run script at the end of each tape. The device name and the current volume
-number are passed on the command line. The script must return 0 if 
+Run script at the end of each tape (except for the last one). 
+The device name and the current volume number are passed on the
+command line. The script must return 0 if 

 .B dump
 should continue without asking the user to change the tape, 1 if 
 .B dump
 .B dump
 should continue without asking the user to change the tape, 1 if 
 .B dump


@@ -224,6 +230,8 @@ is useful when running
 .B dump
 on an active filesystem where read errors simply indicate an inconsistency 
 between the mapping and dumping passes.
 .B dump
 on an active filesystem where read errors simply indicate an inconsistency 
 between the mapping and dumping passes.

+.IP
+A value of 0 means that all read errors will be ignored.

 .TP
 .BI \-j "compression level"
 Compress every block to be written on the tape using bzlib library. This option
 .TP
 .BI \-j "compression level"
 Compress every block to be written on the tape using bzlib library. This option