another question about dump & restore

[Don Speck]

In article <3339 at phri.UUCP>, roy at phri.UUCP (Roy Smith) writes:
>			  I believe there have been some mods to the 4.2BSD
> dump posted (probably by Don Speck, and probably included in the 4.3
> version of dump) which help make dump more immune to file system activity.

Those mods pre-date the parts that I did.  I first saw them in the
"mass-driver" diffs that Chris Torek sent me in January 1985.  They
skip inodes that have been zeroed (deleted) during the dump, as
opposed to the Purdue mods, which also skip inodes whose st_mtime
has changed (such as /dev/tty and /dev/rmt8).

To see how much difference the 4.3 mods made, I copied a small filesystem
to /usr/tmp, then started a simultaneous dump to tape and "rm -r".
Restore would dump core after typically 20% of each tape made by 4.2 dump,
but typically made it through 80% (and sometimes all) of each tape made
by 4.3 dump.  Part of the difference is that 4.3 dump finished before the
"rm -r", so the filesystem was not modified as much during the dump.

An "active filesystem" is one suffering deletions, renamings, and (to
a smaller extent) truncations.	Dump will not see files created during
the dump, and restore should not care about access times being updated.
Directories changing between passes II and III is what confuses restore.

By way of illustration, I once modified dump to start on the mapping
passes while the first tape was being mounted.	Restore choked on dumps
started right before the operator's meal break, which was putting a
one-hour wait between passes II and III.

Don Speck   speck at vlsi.caltech.edu  {amdahl,ames!elroy}!cit-vax!speck