-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zpool events
does not list DEGRADED state change for pool
#12629
Comments
zpool events
does not list DEGRADED state change for polzpool events
does not list DEGRADED state change for pool
Should this have been closed? It doesn't seem like the commit would fix |
@freqlabs is right, this should not have been closed. The PR is related but does not fix this issue. |
Right, a little over zealous. Reopening. |
`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 openzfs#12629 Closes openzfs#12630
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
System information
Describe the problem you're observing
When a pool goes into DEGRADED due to a missing drive, the corresponding statechange event is not generated.
Describe how to reproduce the problem
My pool looks like this:
I wanted to verify that ZED sends emails correctly when the pool is degraded. To do that, I kill one of the drives like so:
And the status changes to degraded as expected:
However,
zpool events -v
does not include a statechange event to DEGRADED for the pool. It does include an UNAVAIL statechange event for the drive itself. However, the default zedletstatechange-notify.sh
only catches'DEGRADED', 'FAULTED' or 'REMOVED'
.There is an argument to be made that
statechange-notify.sh
should also catchUNAVAIL
, but I still think that the statechange event for the pool going to DEGRADED should be generated.Here is the list of relevant events:
The text was updated successfully, but these errors were encountered: