Lines Matching refs:extent

6 extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
31 those on disk - that is, the logical offset of the 1st returned extent
33 extent may end after fm_length. All offsets and lengths are in bytes.
73 fm_extent_count. In that case, the last extent in the array will not
75 flag set (see the next section on extent flags).
77 Each extent is described by a single fiemap_extent structure as
82 			      * the extent */
84 			      * of the extent */
85 	__u64	fe_length;   /* length in bytes for the extent */
87 	__u32	fe_flags;    /* FIEMAP_EXTENT_* flags for this extent */
98 The fe_flags field contains flags which describe the extent returned.
99 A special flag, FIEMAP_EXTENT_LAST is always set on the last extent in
118 This is the last extent in the file. A mapping attempt past this
119 extent will return nothing.
122 The location of this extent is currently unknown. This may indicate
128 Delayed allocation - while there is data for this extent, its
132 This extent does not consist of plain filesystem blocks but is
134 extent via I/O to the block device will have undefined results.
141 extent data via I/O to the block device while the filesystem is
148 The data in this extent has been encrypted by the file system.
162 Unwritten extent - the extent is allocated but its data has not been
163 initialized.  This indicates the extent's data will be all zero if read
169 based addressing scheme.  Since returning an extent for each block back to
180 each discovered extent:
216 For each extent in the request range, the file system should call
223 next free extent in the fm_extents array. 'General' extent flags will
229 while copying the extent to user memory, -EFAULT will be returned.