4 .\" The contents of this file are subject to the terms of the
5 .\" Common Development and Distribution License (the "License").
6 .\" You may not use this file except in compliance with the License.
8 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
9 .\" or https://opensource.org/licenses/CDDL-1.0.
10 .\" See the License for the specific language governing permissions
11 .\" and limitations under the License.
13 .\" When distributing Covered Code, include this CDDL HEADER in each
14 .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
15 .\" If applicable, add the following below this CDDL HEADER, with the
16 .\" fields enclosed by brackets "[]" replaced with your own identifying
17 .\" information: Portions Copyright [yyyy] [name of copyright owner]
21 .\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
22 .\" Copyright (c) 2012, 2018 by Delphix. All rights reserved.
23 .\" Copyright (c) 2012 Cyril Plisko. All Rights Reserved.
24 .\" Copyright (c) 2017 Datto Inc.
25 .\" Copyright (c) 2018 George Melikov. All Rights Reserved.
26 .\" Copyright 2017 Nexenta Systems, Inc.
27 .\" Copyright (c) 2017 Open-E, Inc. All Rights Reserved.
28 .\" Copyright (c) 2021, Colm Buckley <colm@tuatha.org>
29 .\" Copyright (c) 2023, Klara Inc.
37 .Nd properties of ZFS storage pools
40 Each pool has several properties associated with it.
41 Some properties are read-only statistics while others are configurable and
42 change the behavior of the pool.
44 User properties have no effect on ZFS behavior.
45 Use them to annotate pools in a way that is meaningful in your environment.
46 For more information about user properties, see the
50 The following are read-only properties:
51 .Bl -tag -width "unsupported@guid"
53 Amount of storage used within the pool.
60 The ratio of the total amount of storage that would be required to store all
61 the cloned blocks without cloning to the actual storage used.
64 property is calculated as:
66 .Sy ( ( bclonesaved + bcloneused ) * 100 ) / bcloneused
68 The amount of additional storage that would be required if block cloning
71 The amount of storage used by cloned blocks.
73 Percentage of pool space used.
74 This property can also be referred to by its shortened column name,
77 Total size of the deduplication table currently loaded into the ARC.
79 .Xr zpool-prefetch 8 .
80 .It Sy dedup_table_size
81 Total on-disk size of the deduplication table.
83 Amount of uninitialized space within the pool or device that can be used to
84 increase the total capacity of the pool.
85 On whole-disk vdevs, this is the space beyond the end of the GPT –
86 typically occurring when a LUN is dynamically expanded
87 or a disk replaced with a larger one.
88 On partition vdevs, this is the space appended to the partition after it was
89 added to the pool – most likely by resizing it in-place.
90 The space can be claimed for the pool by bringing it online with
93 .Nm zpool Cm online Fl e .
95 The amount of fragmentation in the pool.
96 As the amount of space
98 increases, it becomes more difficult to locate
101 This may result in lower write performance compared to pools with more
102 unfragmented free space.
104 The amount of free space available in the pool.
108 property describes how much new data can be written to ZFS filesystems/volumes.
111 property is not generally useful for this purpose, and can be substantially more
115 This discrepancy is due to several factors, including raidz parity;
116 zfs reservation, quota, refreservation, and refquota properties; and space set
121 for more information).
123 After a file system or snapshot is destroyed, the space it was using is
124 returned to the pool asynchronously.
126 is the amount of space remaining to be reclaimed.
133 A unique identifier for the pool.
135 The current health of the pool.
137 .Sy ONLINE , DEGRADED , FAULTED , OFFLINE, REMOVED , UNAVAIL .
139 Space not released while
141 due to corruption, now permanently leaked into the pool.
143 A unique identifier for the pool.
146 property, this identifier is generated every time we load the pool (i.e. does
147 not persist across imports/exports) and never changes while the pool is loaded
150 operation takes place).
152 Total size of the storage pool.
153 .It Sy unsupported@ Ns Em guid
154 Information about unsupported features that are enabled on the pool.
160 The space usage properties report actual physical space available to the
162 The physical space can be different from the total amount of space that any
163 contained datasets can actually use.
164 The amount of space used in a raidz configuration depends on the characteristics
165 of the data being written.
166 In addition, ZFS reserves some space for internal accounting that the
168 command takes into account, but the
171 For non-full pools of a reasonable size, these effects should be invisible.
172 For small pools, or pools that are close to being completely full, these
173 discrepancies may become more noticeable.
175 The following property can be set at creation time and import time:
178 Alternate root directory.
179 If set, this directory is prepended to any mount points within the pool.
180 This can be used when examining an unknown pool where the mount points cannot be
181 trusted, or in an alternate boot environment, where the typical paths are not
184 is not a persistent property.
185 It is valid only while the system is up.
189 .Sy cachefile Ns = Ns Sy none ,
190 though this may be overridden using an explicit setting.
193 The following property can be set only at import time:
195 .It Sy readonly Ns = Ns Sy on Ns | Ns Sy off
198 the pool will be imported in read-only mode.
199 This property can also be referred to by its shortened column name,
203 The following properties can be set at creation time and import time, and later
208 .It Sy ashift Ns = Ns Ar ashift
209 Pool sector size exponent, to the power of
211 (internally referred to as
213 Values from 9 to 16, inclusive, are valid; also, the
214 value 0 (the default) means to auto-detect using the kernel's block
215 layer and a ZFS internal exception list.
216 I/O operations will be aligned to the specified size boundaries.
217 Additionally, the minimum (disk)
218 write size will be set to the specified size, so this represents a
219 space/performance trade-off.
220 For optimal performance, the pool sector size should be greater than
221 or equal to the sector size of the underlying disks.
222 The typical case for setting this property is when
223 performance is important and the underlying disks use 4KiB sectors but
224 report 512B sectors to the OS (for compatibility reasons); in that
226 .Sy ashift Ns = Ns Sy 12
228 .Sy 1<<12 No = Sy 4096 ) .
229 When set, this property is
230 used as the default hint value in subsequent vdev operations (add,
232 Changing this value will not modify any existing
233 vdev, not even on disk replacement; however it can be used, for
234 instance, to replace a dying 512B sectors disk with a newer 4KiB
235 sectors device: this will probably result in bad performance but at the
236 same time could prevent loss of data.
237 .It Sy autoexpand Ns = Ns Sy on Ns | Ns Sy off
238 Controls automatic pool expansion when the underlying LUN is grown.
241 the pool will be resized according to the size of the expanded device.
242 If the device is part of a mirror or raidz then all devices within that
243 mirror/raidz group must be expanded before the new space is made available to
245 The default behavior is
247 This property can also be referred to by its shortened column name,
249 .It Sy autoreplace Ns = Ns Sy on Ns | Ns Sy off
250 Controls automatic device replacement.
253 device replacement must be initiated by the administrator by using the
258 any new device, found in the same physical location as a device that previously
259 belonged to the pool, is automatically formatted and replaced.
260 The default behavior is
262 This property can also be referred to by its shortened column name,
264 Autoreplace can also be used with virtual disks (like device
265 mapper) provided that you use the /dev/disk/by-vdev paths setup by
269 manual page for more details.
270 Autoreplace and autoonline require the ZFS Event Daemon be configured and
274 manual page for more details.
275 .It Sy autotrim Ns = Ns Sy on Ns | Ns Sy off
278 space which has been recently freed, and is no longer allocated by the pool,
279 will be periodically trimmed.
280 This allows block device vdevs which support
281 BLKDISCARD, such as SSDs, or file vdevs on which the underlying file system
282 supports hole-punching, to reclaim unused blocks.
283 The default value for this property is
286 Automatic TRIM does not immediately reclaim blocks after a free.
287 Instead, it will optimistically delay allowing smaller ranges to be aggregated
288 into a few larger ones.
289 These can then be issued more efficiently to the storage.
290 TRIM on L2ARC devices is enabled by setting
291 .Sy l2arc_trim_ahead > 0 .
293 Be aware that automatic trimming of recently freed data blocks can put
294 significant stress on the underlying storage devices.
295 This will vary depending of how well the specific device handles these commands.
296 For lower-end devices it is often possible to achieve most of the benefits
297 of automatic trimming by running an on-demand (manual) TRIM periodically
301 .It Sy bootfs Ns = Ns Sy (unset) Ns | Ns Ar pool Ns Op / Ns Ar dataset
302 Identifies the default bootable dataset for the root pool.
303 This property is expected to be set mainly by the installation and upgrade
305 Not all Linux distribution boot processes use the bootfs property.
306 .It Sy cachefile Ns = Ns Ar path Ns | Ns Sy none
307 Controls the location of where the pool configuration is cached.
308 Discovering all pools on system startup requires a cached copy of the
309 configuration data that is stored on the root file system.
310 All pools in this cache are automatically imported when the system boots.
311 Some environments, such as install and clustering, need to cache this
312 information in a different location so that pools are not automatically
314 Setting this property caches the pool configuration in a different location that
315 can later be imported with
316 .Nm zpool Cm import Fl c .
317 Setting it to the value
319 creates a temporary pool that is never cached, and the
322 uses the default location.
324 Multiple pools can share the same cache file.
325 Because the kernel destroys and recreates this file when pools are added and
326 removed, care should be taken when attempting to access this file.
327 When the last pool using a
329 is exported or destroyed, the file will be empty.
330 .It Sy comment Ns = Ns Ar text
331 A text string consisting of printable ASCII characters that will be stored
332 such that it is available even if the pool becomes faulted.
333 An administrator can provide additional information about a pool using this
335 .It Sy compatibility Ns = Ns Sy off Ns | Ns Sy legacy Ns | Ns Ar file Ns Oo , Ns Ar file Oc Ns …
336 Specifies that the pool maintain compatibility with specific feature sets.
339 (or unset) compatibility is disabled (all features may be enabled); when set to
341 no features may be enabled.
342 When set to a comma-separated list of filenames
343 (each filename may either be an absolute path, or relative to
344 .Pa /etc/zfs/compatibility.d
346 .Pa /usr/share/zfs/compatibility.d )
347 the lists of requested features are read from those files, separated by
348 whitespace and/or commas.
349 Only features present in all files may be enabled.
352 .Xr zpool-features 7 ,
356 for more information on the operation of compatibility feature sets.
357 .It Sy dedup_table_quota Ns = Ns Ar number Ns | Ns Sy none Ns | Ns Sy auto
358 This property sets a limit on the on-disk size of the pool's dedup table.
359 Entries will not be added to the dedup table once this size is reached;
360 if a dedup table already exists, and is larger than this size, they
361 will not be removed as part of setting this property.
362 Existing entries will still have their reference counts updated.
364 The actual size limit of the table may be above or below the quota,
365 depending on the actual on-disk size of the entries (which may be
366 approximated for purposes of calculating the quota).
367 That is, setting a quota size of 1M may result in the maximum size being
368 slightly below, or slightly above, that value.
372 In automatic mode, which is the default, the size of a dedicated dedup vdev
373 is used as the quota limit.
376 .Sy dedup_table_quota
377 property works for both legacy and fast dedup tables.
378 .It Sy dedupditto Ns = Ns Ar number
379 This property is deprecated and no longer has any effect.
380 .It Sy delegation Ns = Ns Sy on Ns | Ns Sy off
381 Controls whether a non-privileged user is granted access based on the dataset
382 permissions defined on the dataset.
385 for more information on ZFS delegated administration.
386 .It Sy failmode Ns = Ns Sy wait Ns | Ns Sy continue Ns | Ns Sy panic
387 Controls the system behavior in the event of catastrophic pool failure.
388 This condition is typically a result of a loss of connectivity to the underlying
389 storage device(s) or a failure of all devices within the pool.
390 The behavior of such an event is determined as follows:
391 .Bl -tag -width "continue"
393 Blocks all I/O access until the device connectivity is recovered and the errors
396 This is the default behavior.
400 to any new write I/O requests but allows reads to any of the remaining healthy
402 Any write requests that have yet to be committed to disk would be blocked.
404 Prints out a message to the console and generates a system crash dump.
406 .It Sy feature@ Ns Ar feature_name Ns = Ns Sy enabled
407 The value of this property is the current state of
409 The only valid value when setting this property is
413 to the enabled state.
416 for details on feature states.
417 .It Sy listsnapshots Ns = Ns Sy on Ns | Ns Sy off
418 Controls whether information about snapshots associated with this pool is
426 This property can also be referred to by its shortened name,
428 .It Sy multihost Ns = Ns Sy on Ns | Ns Sy off
429 Controls whether a pool activity check should be performed during
430 .Nm zpool Cm import .
431 When a pool is determined to be active it cannot be imported, even with the
434 This property is intended to be used in failover configurations
435 where multiple hosts have access to a pool on shared storage.
437 Multihost provides protection on import only.
438 It does not protect against an
439 individual device being used in multiple pools, regardless of the type of vdev.
440 See the discussion under
441 .Nm zpool Cm create .
443 When this property is on, periodic writes to storage occur to show the pool is
446 .Sy zfs_multihost_interval
450 In order to enable this property each host must set a unique hostid.
455 for additional details.
458 .It Sy version Ns = Ns Ar version
459 The current on-disk version of the pool.
460 This can be increased, but never decreased.
461 The preferred method of updating pools is with the
463 command, though this property can be used when a specific version is needed for
464 backwards compatibility.
465 Once feature flags are enabled on a pool this property will no longer have a
470 In addition to the standard native properties, ZFS supports arbitrary user
472 User properties have no effect on ZFS behavior, but applications or
473 administrators can use them to annotate pools.
475 User property names must contain a colon
477 character to distinguish them from native properties.
478 They may contain lowercase letters, numbers, and the following punctuation
487 The expected convention is that the property name is divided into two portions
489 .Ar module : Ns Ar property ,
490 but this namespace is not enforced by ZFS.
491 User property names can be at most 255 characters, and cannot begin with a dash
494 When making programmatic use of user properties, it is strongly suggested to use
495 a reversed DNS domain name for the
497 component of property names to reduce the chance that two
498 independently-developed packages use the same property name for different
501 The values of user properties are arbitrary strings and
503 All of the commands that operate on properties
504 .Po Nm zpool Cm list ,
509 can be used to manipulate both native properties and user properties.
511 .Nm zpool Cm set Ar name Ns =
512 to clear a user property.
513 Property values are limited to 8192 bytes.