mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2026-01-14 09:12:11 +03:00
4a7a04630d
Historically, ZED has blindly spawned off zedlets in parallel and never worried about their completion order. This means that you can potentially have zedlets for event number 2 starting before zedlets for event number 1 had finished. Most of the time this is fine, and it actually helps a lot when the system is getting spammed with hundreds of events. However, there are times when you want your zedlets to be executed in sequence with the event ID. That is where synchronous zedlets come in. ZED will wait for all previously spawned zedlets to finish before running a synchronous zedlet. Synchronous zedlets are guaranteed to be the only zedlet running. No other zedlets may run in parallel with a synchronous zedlet. Users should be careful to only use synchronous zedlets when needed, since they decrease parallelism. To make a zedlet synchronous, simply add a "-sync-" immediately following the event name in the zedlet's file name: EVENT_NAME-sync-ZEDLETNAME.sh For example, if you wanted a synchronous statechange script: statechange-sync-myzedlet.sh Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Tony Hutter <hutter2@llnl.gov> Closes #17335 |
||
|---|---|---|
| .. | ||
| agents | ||
| zed.d | ||
| .gitignore | ||
| Makefile.am | ||
| zed_conf.c | ||
| zed_conf.h | ||
| zed_disk_event.c | ||
| zed_disk_event.h | ||
| zed_event.c | ||
| zed_event.h | ||
| zed_exec.c | ||
| zed_exec.h | ||
| zed_file.c | ||
| zed_file.h | ||
| zed_log.c | ||
| zed_log.h | ||
| zed_strings.c | ||
| zed_strings.h | ||
| zed.c | ||
| zed.h | ||