Lines Matching full:are

10 directories.  Inodes in the system are very small and all blocks are packed to
11 minimise data overhead. Block sizes greater than 4K are supported up to a
51 directory data are highly compacted, and packed on byte boundaries.  Each
100 Compressed data blocks are written to the filesystem as files are read from
103 xattr tables are written.
110 these are stored here.
115 Metadata (inodes and directories) are compressed in 8Kbyte blocks.  Each
120 Inodes are packed into the metadata blocks, and are not aligned to block
121 boundaries, therefore inodes overlap compressed blocks.  Inodes are identified
126 To maximise compression there are different inodes for each file type
131 directory inode are defined: inodes optimised for frequently occurring
138 Like inodes, directories are packed into compressed metadata blocks, stored
139 in a directory table.  Directories are accessed using the start address of
143 Directories are organised in a slightly complex way, and are not simply
147 Directories are therefore organised in a two level list, a directory
153 Directories are sorted, and can contain a directory index to speed up
156 in each metadata block.  Directories are sorted in alphabetical order,
197 For space efficiency regular files store uid and gid indexes, which are
221 for each inode are stored in a list, each list entry containing a type,
232 The xattr lists are packed into compressed 8K metadata blocks.
249 Blocks in Squashfs are compressed.  To avoid repeatedly decompressing
252 The cache is not used for file datablocks, these are decompressed and cached in
256 are packed together into blocks (to gain greater compression) the read of a
259 read in the near future. Temporarily caching them ensures they are available