Lines Matching full:blocks

16 concepts of blocks, inodes and directories.
23 Blocks
26 The space in the device or file is split up into blocks. These are a fixed
43 are done by copying all modified blocks during that specific write request
51 If the level value is 0, up to 16 direct blocks can be addressed by each
54 addressing block holds up to blocksize / 4 bytes pointers to data blocks.
56 to 16 * 256 * 256 = 1048576 blocks that can be addressed by such a tree).
59 indirect addressing blocks or inodes.
66 information (total number of filesystem blocks) or by taking the highest
77 The inode structure contains pointers to the filesystem blocks which contain
81 size, number of blocks used, access time, change time and modification time.
85 There are also pointers to the first 16 blocks, if the object data can be
86 addressed with 16 direct blocks.
87 For more than 16 blocks an indirect addressing in form of another tree is
158 always uses blocks from the lower half while superblock #2 just writes to
159 blocks represented by the upper half bitmap system area bits.
161 Bitmap blocks, Inode blocks and indirect addressing blocks for those two
162 tree structures are treated as system blocks.
174 For all data outside the system area, blocks are just copied while writing.