piklionx.blogg.se

Openzfs list feature codes
Openzfs list feature codes







openzfs list feature codes
  1. #Openzfs list feature codes upgrade#
  2. #Openzfs list feature codes software#

Precedence over files with the same name in etc/zfs/compatibility.d, if present, will take Popular distributions, and feature sets commonly supported at the start of usr/share/zfs/compatibility.d are provided by theĭistribution, and include feature sets supported by important versions of This is a safety measure to prevent new features from beingĪccidentally enabled, breaking compatibility. This setting also prevents pools from being upgraded to newer on-disk

#Openzfs list feature codes upgrade#

The special value legacy prevents any featuresįrom being enabled, either via zpool upgrade or zpool set feature-name= enabled. zpool status will not show a warning about disabledįeatures which are not part of the requested feature set. Which features are enabled when using zpool upgrade. Zpool create -o compatibility= … and controls The requested features are applied when a pool is created using Simple sanity checks are applied to the files: they must beīetween 1 B and 16 KiB in size, and must end with a newline character. Only features present in all files are enabled. Requested features are read from those files, separated by whitespace and/orĬommas. usr/share/zfs/compatibility.d), the lists of When set to a comma-separated list of filenames (each filename may either be

openzfs list feature codes

all features areĮnabled) when set to legacy, no features are enabled. When set toĭefault), compatibility feature sets are disabled (i.e. The compatibility feature facilitates this byĪllowing feature sets to be read from text files. With a specific on-disk format, by enabling and disabling particularįeatures. It is sometimes necessary for a pool to maintain compatibility Enabling a feature will automatically enable any features it Some features depend on other features being enabled in order toįunction. readonly The feature is read-only compatible and the pool has been imported in

#Openzfs list feature codes software#

Pool's on-disk format is still compatible with software that does not Possible values for this property are: inactive The feature is in the enabled state and therefore the Will indicate why the import was allowed despite the unsupported feature. Property during import (see zpool-import(8) for details onįor each unsupported feature enabled on an imported pool, a pool Imported in read-only mode by setting the readonly Unsupported features on a pool are read-only compatible, the pool can be Theseįeatures are referred to as “read-only compatible”. Interfere with other software's ability to read from the pool. Some features may make on-disk format changes that do not The state of supported features is exposed through pool properties Made unless an administrator moves the feature to theĮnabled state. disabled This feature's on-disk format changes have not been made and will not be See feature-specific documentation forĭetails. Returning to the enabled state after becomingĪctive. Still be imported by software that does not support this feature, butĬhanges may be made to the on-disk format at any time which will move theįeature to the active state. enabled An administrator has marked this feature as enabled on the pool, but theįeature's on-disk format changes have not been made yet. This feature is not read-only compatible, support is also required toĬompatibility). Supportįor this feature is required to import the pool in read-write mode. Short name may differ across ZFS implementations if following the conventionįeatures can be in one of three states: active This feature's on-disk format changes are in effect on the pool. Have the short name feature-name), however a feature's By convention aįeature's short name is the portion of its GUID which follows the Implementation that created the pool for information about thoseĮach supported feature also has a short name. When unsupported features are encountered on a pool they Reversed DNS name ensures that the feature's GUID is unique across all ZFS If the pool was created byĪnother software version this set may include unsupported features. The on-disk format of the pool is specified by the set of all features Since most features can be enabled independently of each other, Or the ability to send file systems between pools. The pool format does not affect file system version compatibility Sets section for information on how sets of features may be enabled Last supported on-disk format number is 28). “features” which replace the old on-disk format numbers (the ZFS pool on-disk format versions are specified via Description of ZFS pool features DESCRIPTION









Openzfs list feature codes