1MKCODABF(1) MKCODABF(1)
2
6 mkcodabf - Make a 'big file' directory tree for Coda
7
9 mkcodabf [-f files-per-dir] [-s hunk-size] [-v] file new-dir
10
13 mkcodabf will take an existing large file and produce a directory tree
14 rooted at new-dir of much smaller files, called hunks. Each hunk,
15 except the last hunk, will be an integral number of megabytes as con‐
16 trolled by the -s flag. The number of hunk files and subdirectories in
17 each directory is controlled by the -f flag. Also, in the directory
18 new-dir, a meta-data file, named _Coda_BigFile_, will be created so
19 that new-dir will appear as a large, read only, regular file after
20 being written to the Coda Distributed File System.
21 The reason for these 'big files' is to allow one to write a very large
23 file, one that is larger than the venus cache, to Coda and to be able
24 to read it back. These are primarily expected to be some kind of media
25 files which are written once and read many times, often in a sequential
26 fashion by a media player. For this reason, file is expected to not be
27 stored in the Coda file tree and new-dir is expected to be in the Coda
28 file tree.
29 mkcodabf supports the following options:
31 -f files-per-dir
33 The number of hunk files or subdirectories in each directory in
34 the 'big file' directory tree. The default number is 100
35 entries per directory.
36 -s hunk-size
38 The size of each hunk file in megabytes. The default hunk size
39 is one megabyte.
40 -v Print verbose output as each directory and file is created. The
42 default is to quietly create the directory tree.
43
45 Currently, only the kernel module for Windows supports 'Big Files'.
46
48 · Philip A. Nelson, August 2006
49Coda Distributed File System 11 August 2006 MKCODABF(1)