zfcp_dbf_rec_run(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– zfcp_dbf_rec_run(9) πŸ’–

okay so bestie, welcome to the zfcp_dbf_rec_run page from the Kernel API Manual β€” yes that's the whole manual name, we're doing this properly πŸŽ€ this is the one about tracing recovery events, and honestly it's short and sweet, so let's get into it ✨


🌸 NAME 🌸

zfcp_dbf_rec_run β€” trace event related to running recovery πŸ¦‹

like, it's the function that drops a trace event when a recovery is actively running. lowkey iconic of it.


✨ SYNOPSIS ✨

void zfcp_dbf_rec_run (char *tag , struct zfcp_erp_action *erp );

that's it. two args. no cap. πŸ’… (and yes, the spacing is exactly like that, we do not touch the code, ever 🫢)


πŸŽ€ ARGUMENTS πŸŽ€

  • tag β€” identifier for event 🏷️ β€” the lil label that tells you what kind of event this is, so future-you (or some poor soul reading the trace) knows what's up
  • erp β€” erp_action running πŸ”₯ β€” the actual zfcp_erp_action that's out there doing the recovery thing, main character energy fr fr

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file ./drivers/s390/scsi/zfcp_dbf.c β€” that's where the whole dbf family lives, and here's the entire squad, no one left behind 🫢:

ngl if you're digging through recovery traces you're gonna end up reading like half of these, so maybe keep this list bookmarked bestie πŸ˜­πŸ’–

and that's the whole vibe check, you're done!! πŸŽ‰ source location is ./drivers/s390/scsi and this page is dated October 2026 β€” go forth and trace those recoveries, mwah πŸ’‹πŸŒˆβ­

πŸ“¦ where this page comes from