Lines Matching refs:extent

8 extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
33 those on disk - that is, the logical offset of the 1st returned extent
35 extent may end after fm_length. All offsets and lengths are in bytes.
75 fm_extent_count. In that case, the last extent in the array will not
77 flag set (see the next section on extent flags).
79 Each extent is described by a single fiemap_extent structure as
84 				* the extent */
86 				* of the extent */
87 	    __u64	fe_length;   /* length in bytes for the extent */
89 	    __u32	fe_flags;    /* FIEMAP_EXTENT_* flags for this extent */
100 The fe_flags field contains flags which describe the extent returned.
101 A special flag, FIEMAP_EXTENT_LAST is always set on the last extent in
120   This is generally the last extent in the file. A mapping attempt past
121   this extent may return nothing. Some implementations set this flag to
122   indicate this extent is the last one in the range queried by the user
126   The location of this extent is currently unknown. This may indicate
133   Delayed allocation - while there is data for this extent, its
137   This extent does not consist of plain filesystem blocks but is
139   extent via I/O to the block device will have undefined results.
146 extent data via I/O to the block device while the filesystem is
153   The data in this extent has been encrypted by the file system.
167   Unwritten extent - the extent is allocated but its data has not been
168   initialized.  This indicates the extent's data will be all zero if read
174   based addressing scheme.  Since returning an extent for each block back to
185 each discovered extent::
223 For each extent in the request range, the file system should call
230 next free extent in the fm_extents array. 'General' extent flags will
236 while copying the extent to user memory, -EFAULT will be returned.