Clarify failmode=wait documentation

Nowhere in the description of the failmode property does it
clearly state how to bring a suspended pool back online.
Add a few words to property description and the zpool-clear(8)
man page.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #12907
Closes #9395
This commit is contained in:
Brian Behlendorf 2022-01-14 15:30:07 -08:00 committed by GitHub
parent 5a57d6f73b
commit 7adc190098
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 3 deletions

View File

@ -337,7 +337,8 @@ The behavior of such an event is determined as follows:
.Bl -tag -width "continue" .Bl -tag -width "continue"
.It Sy wait .It Sy wait
Blocks all I/O access until the device connectivity is recovered and the errors Blocks all I/O access until the device connectivity is recovered and the errors
are cleared. are cleared with
.Nm zpool Cm clear .
This is the default behavior. This is the default behavior.
.It Sy continue .It Sy continue
Returns Returns

View File

@ -44,9 +44,12 @@ Clears device errors in a pool.
If no arguments are specified, all device errors within the pool are cleared. If no arguments are specified, all device errors within the pool are cleared.
If one or more devices is specified, only those errors associated with the If one or more devices is specified, only those errors associated with the
specified device or devices are cleared. specified device or devices are cleared.
If .Pp
If the pool was suspended it will be brought back online provided the
devices can be accessed.
Pools with
.Sy multihost .Sy multihost
is enabled and the pool has been suspended, this will not resume I/O. enabled which have been suspended cannot be resumed.
While the pool was suspended, it may have been imported on While the pool was suspended, it may have been imported on
another host, and resuming I/O could result in pool damage. another host, and resuming I/O could result in pool damage.
. .