BSD 4_3_Reno development
[unix-history] / usr / share / man / cat5 / dumpdates.0
CommitLineData
3922de1d
C
1
2
3
4DUMP(5) 1985 DUMP(5)
5
6
7
8N\bNA\bAM\bME\bE
9 dump, dumpdates - incremental dump format
10
11S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
12 #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<s\bsy\bys\bs/\b/t\bty\byp\bpe\bes\bs.\b.h\bh>\b>
13 #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<s\bsy\bys\bs/\b/i\bin\bno\bod\bde\be.\b.h\bh>\b>
14 #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<p\bpr\bro\bot\bto\boc\bco\bol\bls\bs/\b/d\bdu\bum\bmp\bpr\bre\bes\bst\bto\bor\bre\be.\b.h\bh>\b>
15
16D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
17 Tapes used by _\bd_\bu_\bm_\bp and _\br_\be_\bs_\bt_\bo_\br_\be(8) contain:
18
19 a header record
20 two groups of bit map records
21 a group of records describing directories
22 a group of records describing files
23
24 The format of the header record and of the first record of
25 each description as given in the include file
26 <_\bp_\br_\bo_\bt_\bo_\bc_\bo_\bl_\bs/_\bd_\bu_\bm_\bp_\br_\be_\bs_\bt_\bo_\br_\be._\bh> is:
27
28 #define NTREC 10
29 #define MLEN 16
30 #define MSIZ 4096
31
32 #define TS_TAPE 1
33 #define TS_INODE 2
34 #define TS_BITS 3
35 #define TS_ADDR 4
36 #define TS_END 5
37 #define TS_CLRI 6
38 #define MAGIC (int) 60011
39 #define CHECKSUM (int) 84446
40
41 struct spcl {
42 int c_type;
43 time_t c_date;
44 time_t c_ddate;
45 int c_volume;
46 daddr_t c_tapea;
47 ino_t c_inumber;
48 int c_magic;
49 int c_checksum;
50 struct dinode c_dinode;
51 int c_count;
52 char c_addr[BSIZE];
53 } spcl;
54
55 struct idates {
56 char id_name[16];
57 char id_incno;
58 time_t id_ddate;
59 };
60
61
62
63Printed 7/27/90 June 1
64
65
66
67
68
69
70DUMP(5) 1985 DUMP(5)
71
72
73
74 #define DUMPOUTFMT "%-16s %c %s" /* for printf */
75 /* name, incno, ctime(date) */
76 #define DUMPINFMT "%16s %c %[^\n]\n" /* inverse for scanf */
77
78 NTREC is the number of 1024 byte records in a physical tape
79 block. MLEN is the number of bits in a bit map word. MSIZ
80 is the number of bit map words.
81
82 The TS_ entries are used in the _\bc__\bt_\by_\bp_\be field to indicate
83 what sort of header this is. The types and their meanings
84 are as follows:
85
86 TS_TAPE Tape volume label
87 TS_INODE A file or directory follows. The _\bc__\bd_\bi_\bn_\bo_\bd_\be
88 field is a copy of the disk inode and contains
89 bits telling what sort of file this is.
90 TS_BITS A bit map follows. This bit map has a one bit
91 for each inode that was dumped.
92 TS_ADDR A subrecord of a file description. See _\bc__\ba_\bd_\bd_\br
93 below.
94 TS_END End of tape record.
95 TS_CLRI A bit map follows. This bit map contains a
96 zero bit for all inodes that were empty on the
97 file system when dumped.
98 MAGIC All header records have this number in _\bc__\bm_\ba_\bg_\bi_\bc.
99 CHECKSUM Header records checksum to this value.
100
101 The fields of the header structure are as follows:
102
103 c_type The type of the header.
104 c_date The date the dump was taken.
105 c_ddate The date the file system was dumped from.
106 c_volume The current volume number of the dump.
107 c_tapea The current number of this (1024-byte) record.
108 c_inumber The number of the inode being dumped if this is
109 of type TS_INODE.
110 c_magic This contains the value MAGIC above, truncated
111 as needed.
112 c_checksum This contains whatever value is needed to make
113 the record sum to CHECKSUM.
114 c_dinode This is a copy of the inode as it appears on
115 the file system; see _\bf_\bs(5).
116 c_count The count of characters in _\bc__\ba_\bd_\bd_\br.
117 c_addr An array of characters describing the blocks of
118 the dumped file. A character is zero if the
119 block associated with that character was not
120 present on the file system, otherwise the char-
121 acter is non-zero. If the block was not
122 present on the file system, no block was
123 dumped; the block will be restored as a hole in
124 the file. If there is not sufficient space in
125 this record to describe all of the blocks in a
126
127
128
129Printed 7/27/90 June 2
130
131
132
133
134
135
136DUMP(5) 1985 DUMP(5)
137
138
139
140 file, TS_ADDR records will be scattered through
141 the file, each one picking up where the last
142 left off.
143
144 Each volume except the last ends with a tapemark (read as an
145 end of file). The last volume ends with a TS_END record and
146 then the tapemark.
147
148 The structure _\bi_\bd_\ba_\bt_\be_\bs describes an entry in the file
149 /_\be_\bt_\bc/_\bd_\bu_\bm_\bp_\bd_\ba_\bt_\be_\bs where dump history is kept. The fields of
150 the structure are:
151
152 id_name The dumped filesystem is `/dev/_\bi_\bd__\bn_\ba_\bm'.
153 id_incno The level number of the dump tape; see _\bd_\bu_\bm_\bp(8).
154 id_ddate The date of the incremental dump in system format
155 see _\bt_\by_\bp_\be_\bs(5).
156
157F\bFI\bIL\bLE\bES\bS
158 /etc/dumpdates
159
160S\bSE\bEE\bE A\bAL\bLS\bSO\bO
161 dump(8), restore(8), fs(5), types(5)
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195Printed 7/27/90 June 3
196
197
198