Lines Matching refs:directory
34 Max entries per directory unlimited unlimited
51 directory data are highly compacted, and packed on byte boundaries. Each
53 file type, i.e. regular file, directory, symbolic link, and block/char device
144 | directory |
161 the source directory, and checked for duplicates. Once all file data has been
162 written the completed inode, directory, fragment, export, uid/gid lookup and
187 (regular file, directory, device, etc.), the inode contents and length
191 directory inode are defined: inodes optimised for frequently occurring
199 in a directory table. Directories are accessed using the start address of
200 the metablock containing the directory and the offset into the
207 Directories are therefore organised in a two level list, a directory
208 header containing the shared start block value, and a sequence of directory
209 entries, each of which share the shared start block. A new directory header
210 is written once/if the inode start block changes. The directory
211 header/directory entry list is repeated as many times as necessary.
213 Directories are sorted, and can contain a directory index to speed up
215 storing the index/filename mapping to the first directory header
221 decompressed to do a lookup irrespective of the length of the directory.
315 (i.e. inode or directory) or fragment access. Because metadata and fragments