Lines Matching refs:blocks

19 concepts of blocks, inodes and directories.
31 The space in the device or file is split up into blocks. These are a fixed
49 are done by copying all modified blocks during that specific write request
57 If the level value is 0, up to 16 direct blocks can be addressed by each
61 addressing block holds up to blocksize / 4 bytes pointers to data blocks.
63 to 16 * 256 * 256 = 1048576 blocks that can be addressed by such a tree).
66 indirect addressing blocks or inodes.
75 information (total number of filesystem blocks) or by taking the highest
86 The inode structure contains pointers to the filesystem blocks which contain
90 size, number of blocks used, access time, change time and modification time.
94 There are also pointers to the first 16 blocks, if the object data can be
95 addressed with 16 direct blocks.
97 For more than 16 blocks an indirect addressing in form of another tree is
180 always uses blocks from the lower half while superblock #2 just writes to
181 blocks represented by the upper half bitmap system area bits.
183 Bitmap blocks, Inode blocks and indirect addressing blocks for those two
184 tree structures are treated as system blocks.
196 For all data outside the system area, blocks are just copied while writing.