Lines Matching full:features

53  * Within each pool features can be in one of three states: disabled, enabled,
74  * It is the responsibility of the individual features to maintain a non-zero
80  * Each feature may depend on other features. The only effect of this
83  * features would need to ensure that features cannot be disabled if other
84  * enabled features depend on them.
94  * Information about features is stored in 3 ZAP objects in the pool's MOS.
99  *    Features needed to open the pool for reading.
101  *    Features needed to open the pool for writing.
105  * All enabled features appear in either features_for_read or
108  * To open a pool in read-only mode only the features listed in
111  * To open the pool in read-write mode features in both features_for_read and
114  * Some features may be required to read the ZAP objects containing feature
115  * information. To allow software to check for compatibility with these features
117  * new "features_for_read" entry (note that features that are only required
120  * To save space in the label features must be explicitly marked as needing to
125  * Adding New Features
128  * Features must be registered in zpool_feature_init() function in
141  * Features may not perform enable-time initialization. Instead, any such
143  * enforces that on-disk changes be made only when features are used. Code
169  * Checks that the active features in the pool are supported by
221  * Note: well-designed features will not need to use this; they should
238  * Note: well-designed features will not need to use this; they should
253 	 * have been allocated yet.  Act as though all features are disabled.  in feature_get_refcount_from_disk()
308 	 * creation of arbitrary features whose fi_feature field may  in feature_sync()