mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2024-12-25 18:59:33 +03:00
Improve the wording about hot spares
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
This commit is contained in:
parent
6b92390fe8
commit
0d122e21ff
@ -380,7 +380,7 @@ If a device is removed and later re-attached to the system, \fBZFS\fR attempts t
|
||||
|
||||
.sp
|
||||
.LP
|
||||
Spares can be shared across multiple pools, and can be added with the "\fBzpool add\fR" command and removed with the "\fBzpool remove\fR" command. Once a spare replacement is initiated, a new "spare" \fBvdev\fR is created within the configuration that will remain there until the original device is replaced. At this point, the hot spare becomes available again if another device fails.
|
||||
Spares can be shared across multiple pools, and can be added with the "\fBzpool add\fR" command and removed with the "\fBzpool remove\fR" command. Once a spare replacement is initiated, a new "spare" \fBvdev\fR is created within the configuration that will remain there until the original device is replaced. At this point, the hot spare becomes available again.
|
||||
.sp
|
||||
.LP
|
||||
If a pool has a shared spare that is currently being used, the pool can not be exported since other pools may use this shared spare, which may lead to potential data corruption.
|
||||
@ -1640,7 +1640,7 @@ If one of the disks were to fail, the pool would be reduced to the degraded stat
|
||||
|
||||
.sp
|
||||
.LP
|
||||
Once the data has been resilvered, the spare is automatically removed and is made available should another device fails. The hot spare can be permanently removed from the pool using the following command:
|
||||
Once the data has been resilvered, the spare is automatically removed and is made available for use should another device fails. The hot spare can be permanently removed from the pool using the following command:
|
||||
|
||||
.sp
|
||||
.in +2
|
||||
|
Loading…
Reference in New Issue
Block a user