Manpage of UNTRACE

UNTRACE

Section: User Commands (1) Updated: Feb 10, 1992 Return to Library's README

NAME

untrace -- recreate actions from a trace

SYNOPSIS

untrace [ -d ] [ -f filterfile ] [ -m ] [ -r replayfile ] 
        [ -s skeletonfile ] [ -v ] [ -xp ] file

DESCRIPTION

untrace reads the trace in file and attempts to reconstruct the actions in the trace. The program outputs two files -- a skeleton file and a replay file. The skeleton file contains commands to build a skeleton of the file system needed for the trace actions to be replayed. The replay file contains those actions. The command files may be replayed by creplay. The program makes two passes over the input tracefile. The first simply builds data structures which allow the set of skeleton-building commands to be emitted at completion. The second pass emits the replay commands as it processes each record.

OPTIONS

: -d Delta for think time, in seconds. If the time difference trace records is greated than this value, a delay of the difference will be inserted.
: -f filterfile Apply the filter in filterfile to the trace.
: -m Consider only mutations to objects in the file system.
: -r replayfile Name of the file in which to put the commands that replay actions in the trace. Default is replay.cmd.
: -s skeletonfile Name of the file in which to put the commands that build the file system structure in which the trace actions occurred. Default is skeleton.cmd.
: -v Verbose mode. Prints the number of records handled in units of 100, messages about interesting inferences, and the structure of the file system skeleton at the end of the first pass.
: -x Allow cross parent links. Default is to leave them out, as they will cause the execution of the command file to fail in AFS or CFS.

DIAGNOSTICS

The following are frequently encountered errors:

can't process file file -- the file wasn't there or if a filter file was specified, it couldn't be applied.

BUGS

Doesn't handle MOUNT or UNMOUNT records. If either of these is encountered, the program assertion fails.

A filter file containing the commands in untrace.fil must be used for correct matching of open and close calls. These settings really should be specified in the program.

Filtering other than that used in untrace.fil should be used with extreme care. It is is helpful only if the filtered actions are local. Otherwise, one might be filtering out information needed to build the file system skeleton.

There are many wierd cases that haven't been tested. The program will assertion fail if it encounters one.

AUTHOR

Original version by James J. Kistler. Updates and minor bug fixes by Lily B. Mummert.

This document was created on Time: 05:25:52 GMT, October 10, 1998