Lines Matching refs:extent

38 led to the creation of the extent mapping scheme, discussed below.
46 In ext4, the file to logical block map has been replaced with an extent
51 very large files with a single extent, at a considerable reduction in
60 points to a block containing more nodes in the extent tree. If the node
63 point to the file's data blocks. The root node of the extent tree is
67 The extent tree header is recorded in ``struct ext4_extent_header``,
93      - Depth of this extent node in the extent tree. 0 = this extent node
94        points to data blocks; otherwise, this extent node points to other
95        extent nodes. The extent tree can be at most 5 levels deep: a logical
103 Internal nodes of the extent tree, also known as index nodes, are
121      - Lower 32-bits of the block number of the extent node that is the next
133 Leaf nodes of the extent tree are recorded as ``struct ext4_extent``,
147      - First file block number that this extent covers.
151      - Number of blocks covered by extent. If the value of this field is <=
152        32768, the extent is initialized. If the value of the field is > 32768,
153        the extent is uninitialized and the actual extent length is ``ee_len`` -
154        32768. Therefore, the maximum length of a initialized extent is 32768
155        blocks, and the maximum length of an uninitialized extent is 32767.
159      - Upper 16-bits of the block number to which this extent points.
163      - Lower 32-bits of the block number to which this extent points.
165 Prior to the introduction of metadata checksums, the extent header +
166 extent entries always left at least 4 bytes of unallocated space at the
167 end of each extent tree data block (because (2^x % 12) >= 4). Therefore,
171 inode generation, and the entire extent block leading up to (but not
187      - Checksum of the extent block, crc32c(uuid+inum+igeneration+extentblock)