OCF_HEARTBEAT_NFSNOT(7)

💖 ocf_heartbeat_nfsnotify(7) — like, the whole manual, bestie

hey bestie 🫶 so this is a page from the OCF resource agents manuals, and it's literally all about nfsnotify — the sm-notify reboot notifications situation. sit down, grab a strawberry drink 🍓, we're getting into it.

---

✨ NAME ✨

okay so, the star of the show: ocf_heartbeat_nfsnotify — and what it does is sm-notify reboot notifications. that's the vibe. 💅

---

🌸 SYNOPSIS 🌸

nfsnotify [start | stop | monitor | meta-data | validate-all]

like, those are your moves. pick one. 👑

---

🦋 DESCRIPTION 🦋

so what does this agent actually do, you ask? it sends NFSv3 reboot notifications to clients — which is the polite way of informing those clients that they should reclaim their locks. it's giving "hey girl, we rebooted, come get your stuff back" energy. 💌

---

🎀 SUPPORTED PARAMETERS 🎀

these are the knobs you can turn. read them carefully, no cap:

• source_host — a comma separated list of floating IP addresses or host names that clients use to access the nfs service. this bad boy is what gets used to set the source address and the mon_name of the SN_NOTIFY reboot notifications. (optional, string, no default) ✨
• statd_path — path to the directory where the statd state lives. heads up: this needs to be on shared storage, fr fr. (optional, string, default "/var/lib/nfs/statd") 🗂️
• notify_args — extra arguments to send to the sm-notify command. by default this agent will always set sm-notify's '-f' option. when the source_host option is set, the '-v' option gets used automatically to set the proper source address. any additional sm-notify arguments you set with this option get used in addition to the previous default arguments. (optional, string, no default) 🔥
• statd_path — okay so this one is, literally, listed again: path to the directory in which the statd state lives, and it needs to be on shared storage. (optional, string, default "/var/lib/nfs/statd"). yes bestie, it shows up twice on the page — we don't question the source, we just report it. 🙈

---

⭐ SUPPORTED ACTIONS ⭐

this resource agent supports the following actions (operations) — main character energy only:

1. start — starts the resource. suggested minimum timeout: 90s. 🚀
2. **stop``** — stops the resource. suggested minimum timeout: 90s`. 🛑
3. monitor — performs a detailed status check. suggested minimum timeout: 90s. suggested interval: 30s. 👀
4. reload — suggested minimum timeout: 90s. 🔄
5. meta-data — retrieves resource agent metadata (internal use only, iykyk). suggested minimum timeout: 10s. 🤫
6. validate-all — performs a validation of the resource configuration. suggested minimum timeout: 20s. ✅

ngl, the timeouts are the whole personality here. respect them.

---

🌈 EXAMPLE CRM SHELL 🌈

here's an example config for a nfsnotify resource using the crm(8) shell — copy it exactly, don't freestyle:

primitive p_nfsnotify ocf:heartbeat:nfsnotify \
  op monitor timeout="90s" interval="30s" depth="0"

ate. 💅

---

🧚 EXAMPLE PCS 🧚

and here's the same kinda energy for pcs(8):

pcs resource create p_nfsnotify ocf:heartbeat:nfsnotify \
  op monitor timeout="90s" interval="30s" OCF_CHECK_LEVEL="0"

two examples, two icons, both iconic. 👑

---

💜 SEE ALSO 💜

• http://clusterlabs.org/ — go say hi, the clusterlabs girlies live there. 🌐

---

👑 AUTHOR 👑

ClusterLabs contributors — see the resource agent source for information about individual authors. credit where credit is due, always. 🫶

---

okay that's the whole page, periodt. 💖 this gorgeousness is from resource-agents, version UNKNOWN, dated 10/01/2026 — so go forth, notify those reboots, reclaim those locks, and slay. 🌸💅✨