diff options
| author | Francesco Mazzoli <[email protected]> | 2021-10-16 00:57:23 +0200 |
|---|---|---|
| committer | GitHub <[email protected]> | 2021-10-15 15:57:23 -0700 |
| commit | fd778e44c88fd3215c8a7f5ec4989431ac02cd32 (patch) | |
| tree | 4bae887c15bf48d6d899a9b5c80ae6eac6c7131f | |
| parent | 01b572bc623cec3f7ff4f6ffb2dbf47d28ee7559 (diff) | |
Notify on UNAVAIL statechange
`UNAVAIL` is maybe not quite as concerning as `DEGRADED`, but still an
event of notice, in my opinion. For example it is triggered when a
drive goes missing.
Reviewed-by: Don Brady <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Francesco Mazzoli <[email protected]>
Closes #12629
Closes #12630
| -rwxr-xr-x | cmd/zed/zed.d/statechange-notify.sh | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/cmd/zed/zed.d/statechange-notify.sh b/cmd/zed/zed.d/statechange-notify.sh index 76f09061c..ab11dfbc9 100755 --- a/cmd/zed/zed.d/statechange-notify.sh +++ b/cmd/zed/zed.d/statechange-notify.sh @@ -15,7 +15,7 @@ # Send notification in response to a fault induced statechange # # ZEVENT_SUBCLASS: 'statechange' -# ZEVENT_VDEV_STATE_STR: 'DEGRADED', 'FAULTED' or 'REMOVED' +# ZEVENT_VDEV_STATE_STR: 'DEGRADED', 'FAULTED', 'REMOVED', or 'UNAVAIL' # # Exit codes: # 0: notification sent @@ -31,7 +31,8 @@ if [ "${ZEVENT_VDEV_STATE_STR}" != "FAULTED" ] \ && [ "${ZEVENT_VDEV_STATE_STR}" != "DEGRADED" ] \ - && [ "${ZEVENT_VDEV_STATE_STR}" != "REMOVED" ]; then + && [ "${ZEVENT_VDEV_STATE_STR}" != "REMOVED" ] \ + && [ "${ZEVENT_VDEV_STATE_STR}" != "UNAVAIL" ]; then exit 3 fi |