Lines Matching full:feature
10 If the sparse_super feature flag is set, redundant copies of the
137 Note: the difference between the compatible feature set and the
138 incompatible feature set is that if there is a bit set in the
139 incompatible feature set that the kernel doesn't know about, it should
143 about a feature in either the compatible or incompatible feature set, it
160 - Compatible feature set flags. Kernel can still read/write this fs even
166 - Incompatible feature set. If the kernel or fsck doesn't understand one
172 - Readonly-compatible feature set. If the kernel doesn't understand one of
226 - Device number of journal file, if the external journal feature flag is
250 - Size of group descriptors, in bytes, if the 64bit incompat feature flag
259 - First metablock block group, if the meta_bg feature is enabled.
310 feature does not seem to be implemented...
607 the journal, JBD2 incompat feature
613 entries in the file, we additionally set proper rocompat feature
637 - Meta block groups. See the earlier discussion of this feature
646 - Flexible block groups. See the earlier discussion of this feature
654 - Metadata checksum seed is stored in the superblock. This feature enables
660 this feature, directories could not be larger than 4GiB and could not
661 have an htree more than 2 levels deep. If this feature is enabled,
680 - Sparse superblocks. See the earlier discussion of this feature
715 - Filesystem supports replicas. This feature is neither in the kernel nor