dump(8)'s manual page is confusing in its use of records, blocks,

blocksizes, etc
does not give the default of -b
only mentiones rdump in the NAME section
uses both filesystem and file system in similar contexts

PR:		34248
Submitted by:	Gary W. Swearingen <swear@blarg.net>
MFC after:	3 days
This commit is contained in:
Tom Rhodes 2002-04-17 02:10:33 +00:00
parent 440ed3238b
commit 7ac806655e
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=94911

View File

@ -53,7 +53,11 @@
.Op Fl T Ar date
.Ar filesystem
.Nm
.Op Fl W Li \&| Fl w
.Fl W | Fl w
.Pp
.Nm rdump
is an alternate name for
.Nm .
.Pp
.in \" XXX
(The
@ -83,10 +87,16 @@ On media that cannot reliably return an end-of-media indication
(such as some cartridge tape drives)
each volume is of a fixed size;
the actual size is determined by the tape size and density and/or
block count options below.
.Fl B
options.
By default, the same output file name is used for each volume
after prompting the operator to change media.
.Pp
The filesystem to be dumped is specified by the argument
.Ar filesystem
as either its device-special file or its mount point
(if that is in a standard entry in /etc/fstab).
.Pp
The following options are supported by
.Nm :
.Bl -tag -width Ds
@ -112,11 +122,15 @@ recommended when appending to an existing tape, or using a tape
drive with hardware compression (where you can never be sure about
the compression ratio).
.It Fl B Ar records
The number of 1 KB blocks per volume.
The number of kilobytes per output volume, except that if it is
not an integer multiple of the output block size,
the command uses the next smaller such multiple.
This option overrides the calculation of tape size
based on length and density.
.It Fl b Ar blocksize
The number of kilobytes per dump record.
The number of kilobytes per output block, except that if it is
larger than 64, the command uses 64. (See the BUGS section.)
The default block size is 10.
.It Fl c
Change the defaults for use with a cartridge tape drive, with a density
of 8000 bpi, and a length of 1700 feet.
@ -343,8 +357,7 @@ Always start with a level 0 backup, for example:
This should be done at set intervals, say once a month or once every two months,
and on a set of fresh tapes that is saved forever.
.It
After a level 0, dumps of active file
systems are taken on a daily basis,
After a level 0, dumps of active filesystems are taken on a daily basis,
using a modified Tower of Hanoi algorithm,
with this sequence of dump levels:
.Bd -literal -offset indent
@ -404,7 +417,7 @@ is written.
Currently,
.Xr physio 9
slices all requests into chunks of 64 KB. Therefore, it is
impossible to use a larger tape blocksize, so
impossible to use a larger output block size, so
.Nm
will prevent this from happening.
.Pp