| Main index | Section 8 | Options |
| | |
| Forces use of vdevs, even if they appear in use, have conflicting ashift values, or specify a conflicting replication level. Not all devices can be overridden in this manner. | |
| | |
| Display vdev, GUIDs instead of the normal device names. These GUIDs can be used in place of device names for the zpool detach/offline/remove/replace commands. | |
| | |
| Display real paths for vdevs resolving all symbolic links. This can be used to look up the current block device name regardless of the /dev/disk path used to open it. | |
| | |
| Displays the configuration that would be used without actually adding the vdevs. The actual pool creation can still fail due to insufficient privileges or device sharing. | |
| | |
|
Display real paths for
vdevs
instead of only the last component of the path.
This can be used in conjunction with the
| |
| | |
| Sets the given pool properties. See the zpoolprops(7) manual page for a list of valid properties that can be set. The only property supported at the moment is ashift. | |
| | |
| Disable the ashift validation which allows mismatched ashift values in the pool. Adding top-level vdevs with different sector sizes will prohibit future device removal operations, see zpool-remove(8). | |
| | |
| Allow vdevs to be added even if they might be in use in another pool. | |
| | |
| Allow vdevs with conflicting replication levels to be added to the pool. | |
# zpool
# zpool
Once added, the cache devices gradually fill with content from main memory. Depending on the size of your cache devices, it could take over an hour for them to fill. Capacity and reads can be monitored using the iostat subcommand as follows:
# zpool
| ZPOOL-ADD (8) | March 8, 2024 |
| Main index | Section 8 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.