Lines Matching +full:data +full:- +full:mapping

6 extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
11 --------------
17 				  * which to start mapping (in) */
18 	__u64	fm_length;	 /* logical length of mapping which
31 those on disk - that is, the logical offset of the 1st returned extent
49 fm_extents[] to hold the file's current mapping.  Note that there is
55 If this flag is set, the kernel will sync the file before mapping extents.
59 extended attribute lookup tree, instead of its data tree.
62 Extent Mapping
63 --------------
110 for inline or tail-packed data can key on the specific flag. Software
111 which simply cares not to try operating on non-aligned extents
114 data. Note that the opposite is not true - it would be valid for
118 This is the last extent in the file. A mapping attempt past this
123 the data is stored on an inaccessible volume or that no storage has
127   - This will also set FIEMAP_EXTENT_UNKNOWN.
128 Delayed allocation - while there is data for this extent, its
133 encoded (e.g. encrypted or compressed).  Reading the data in this
136 Note that it is *always* undefined to try to update the data
137 in-place by writing to the indicated location without the
138 assistance of the filesystem, or to access the data using the
141 extent data via I/O to the block device while the filesystem is
147   - This will also set FIEMAP_EXTENT_ENCODED
148 The data in this extent has been encrypted by the file system.
155 Data is located within a meta data block.
159 Data is packed into a block with data from other files.
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
174 VFS -> File System Implementation
175 ---------------------------------
177 File systems wishing to support fiemap must implement a ->fiemap callback on
178 their inode_operations structure. The fs ->fiemap call is responsible for
188 ->fiemap is passed struct fiemap_extent_info which describes the
203 Flag checking should be done at the beginning of the ->fiemap callback via the
211 fieinfo->fi_flags and return -EBADR. If the file system gets -EBADR, from
228 user-supplied fm_extents array is full. If an error is encountered
229 while copying the extent to user memory, -EFAULT will be returned.