|ZPOOL-REPLACE(8)||System Manager's Manual||ZPOOL-REPLACE(8)|
replace one device with another in ZFS storage
Replaces device with new-device. This is equivalent to attaching new-device, waiting for it to resilver, and then detaching device. Any in progress scrub will be cancelled.
The size of new-device must be greater than or equal to the minimum size of all the devices in a mirror or raidz configuration.
new-device is required if the pool is not redundant. If new-device is not specified, it defaults to device. This form of replacement is useful after an existing disk has failed and has been physically replaced. In this case, the new disk may have the same /dev path as the old device, even though it is actually a different disk. ZFS recognizes this.
- Forces use of new-device, even if it appears to be in use. Not all devices can be overridden in this manner.
- 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.
- The new-device is reconstructed sequentially to restore redundancy as quickly as possible. Checksums are not verified during sequential reconstruction so a scrub is started when the resilver completes. Sequential reconstruction is not supported for raidz configurations.
- Waits until the replacement has completed before returning.
|May 29, 2021||OpenZFS|