1CODA_REPLAY(1) CODA_REPLAY(1)
2
3
4
6 coda_replay - Manual reintegration tool
7
9 coda_replay [ key ] filename
10
11
13 coda_replay is a tool for manually reintegrating operations done at a
14 disconnected client. It provides a superset of the functionality of
15 the tape-archive program, tar(1). The key argument is a string of
16 characters containing exactly one function letter and possibly one or
17 more function modifiers. The filename argument specifies the
18 tar/replay format file containing the operations to be replayed.
19
20 The function portion of the key is specified by one of the following
21 letters:
22
23 r Replay all operations specified in the file.
24
25 s Strip out non-tar operations from the file and replay only the
26 tar operations.
27
28 t Do not replay but simply list the operations specified in the
29 file.
30
31 The following characters may be used in addition to the letter which
32 selects the function desired:
33
34 v Be verbose about the operations.
35
36 h Be harsh in replay, i.e., abort the program if any replayed
37 operation fails.
38
39 coda_replay can handle normal tar files since it invokes tar to perform
40 create, link, and symlink operations. However, its main purpose is to
41 replay checkpoint files saved by the Coda cache manager, Venus, during
42 disconnected operation. These files may contain operations unknown to
43 tar: setattr, unlink, rename, mkdir, and rmdir. These other operations
44 are encoded in the tar file by overloading the linkflag and linkname
45 fields. Consult the replay.h header file for more details.
46
48 · There is a limit of 100 characters imposed on filename length by tar.
49
50 · Filenames in checkpoint files generated by Venus are all relative to
51 the enclosing volume root.
52
54 tar(1), tar(5), venus(8)
55
57 · Jay Kistler, 1990, Created
58
59
60
61Coda Distributed File System 25 April 2005 CODA_REPLAY(1)