1dumpfile(5) File Formats Manual dumpfile(5)
2
6 dumpfile - Format of a dump file
7
10 The dump files are formatted as tagged byte streams. Each piece of the
11 dump is marked by a tag byte, a number between 1 and 20. Each piece
12 may also be broken into subpieces, each marked by a letter of the
13 alphabet. Each subpiece is uniquely marked, but tags can be reused in
14 different parts of the dump.
15 The first 60 bytes of the dump contain header information. This header
17 info identifies which backup volume was used to create the dump, and
18 when and from which volume the backup clone was created. It also indi‐
19 cates whether the dump was incremental, and provides information to be
20 used later in placing this dump in the proper sequence for merging.
21 Following the dump header is the volume information structure used by
22 the Coda internals. Following this are two sequences of vnodes, one
23 for directories and one for files. Each sequence consists of a header
24 and a stream of vnodes.
25 The vnode sequence header contains the number of vnodes and the size of
27 the vnode list. These numbers are not necessarily the same since not
28 every list needs to have a vnode on it and some lists may have more
29 than one. This is an artifact of the way vnodes are stored in the Coda
30 servers.
31 After these two fields comes a list of vnodes. Each vnode consists of
33 two parts, the first is the meta information associated with the file
34 or directory and the second is the data for that vnode. This data
35 could either be directory pages or file data. The first word after the
36 tag for the file or directory data is a count of bytes or directory
37 pages. For directory vnodes, the access list for that directory is
38 included as part of the meta information.
39
41 backup (8), dumplist (5), volutil (8)
42
44 Joshua Raiff, 1993, Taken from system adminstrators guide.
45 dumpfile(5)