.th FSD VIII 4/21/86
.sh NAME
fsd - incremental file system dump
.sh SYNOPSIS
fsd filesystem [-0vc] [-e extentseid] [-b blocks] [-d days]
[-f device] [-h hours] 
.sh DESCRIPTION
Fsd makes an incremental dump of all files on the specified KSOS file
system which were changed after a certain date.  Fsd is spawned by the
Secure Server at the request of a user running at OPERATOR or higher
integrity level.  The save medium may be either tape or an existing
KSOS extent.  Fsd opens the file system for exclusive use, thus the
file system must be unmounted prior to running fsd.
.sp
The arguments are as follows:
.lp 13 8
b       The next argument is the maximum size of the save tape (or extent)
in blocks.
.lp 13 8
c       If the dump tape overflows, increment the minor device number
and continue.
Normally, you are asked to change tapes.
.lp 13 8
e       Dump to the specified defined extent instead of to tape.
.lp 13 8
d       The next argument specifies the dump date as some number of days
prior to the current date.
.lp 13 8
f       Use the next argument as the save device
instead of the default (device_nsp, 11, 0).
.lp 13 8
v       Print out the information in the dump header.
.lp 13 8
h	The next argument specifies the dump date as some number of hours
prior to the current date.
.lp 13 8
0       Dump from the beginning of time.
.i0
.sp
.sh DIAGNOSTICS
Generally errors are fatal.  Files found in an unSAFE condition are not
dumped, but the jnode is dumped and the high block field is set to 0.
A message to this effect is printed for each bad file encountered.
.sh FILES
/sys/dataBases/security    system security map
.sh "SEE ALSO"
FSR (VIII), DUMP (V)
.sh NOTES
The d and h options are not implemented - all dumps are from the
beginning of time.  When dumping to an extent, fsd could recover from
most errors.  Unfortunately, fsd's approach is to exit if anything is
wrong.
