OCF_LINBIT_DRBD-ATT(7)

πŸ’– NAME πŸ’–

okay bestie, welcome to OCF_LINBIT_DRBD-ATT(7) β€” yes, that's the manual name, and it's part of the OCF resource agents family. The star of the page is ocf_linbit_drbd-attr, and its whole job is to import DRBD state change events as transient node attributes. That's the main character job, and it ate. ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

Run it like this, bestie:

drbd-attr [start | stop | monitor | meta-data | validate-all]

No cap, that bracket list is the whole vibe check. πŸ’…

🌸 DESCRIPTION 🌸

This icon listens for DRBD state change events, then sets or deletes transient node attributes based on the "promotion_score" and "may_promote" values as presented by the DRBD events2 interface. Literally event-to-attribute behavior, and it's giving useful. 🫢

There's optionally a dampening delay too β€” see attrd_updater for the details, iykyk.

Use this as a clone on all DRBD nodes. The idea is: start DRBD outside of pacemaker, use DRBD auto-promote, and add location constraints for the Filesystem or other resource agents which are using DRBD. That's the plan, periodt. 🌈

πŸŽ€ SUPPORTED PARAMETERS πŸŽ€

  • dampening_delay β€” this is used as the dampening delay in attrd_updater. It's optional, an integer, and the default is 5. Set it and slay. πŸ’…
  • attr_name_prefix β€” the attributes will be named prefix-drbd_resource_name. You can choose that prefix here. It's optional, a string, and the default is "drbd-promotion-score". Obsessed with a customizable prefix, ngl. πŸŽ€
  • record_event_details β€” sometimes it may be convenient to know which event led to the current score. This setting toggles the recording of the event. The attributes will be named prefix:event-details-drbd_resource_name. It's optional, a boolean, and the default is false. Lowkey detective mode for your scores. πŸ”

⭐ SUPPORTED ACTIONS ⭐

This resource agent supports these actions (operations), bestie:

  • start β€” starts the resource. Suggested minimum timeout: 20s. Go go go. πŸš€
  • stop β€” stops the resource. Suggested minimum timeout: 20s. Bye boo. πŸ‘‹
  • monitor β€” performs a detailed status check. Suggested minimum timeout: 20s. Suggested interval: 60s. The vibe check, literally. πŸ•΅οΈβ€β™€οΈ
  • validate-all β€” performs a validation of the resource configuration. Suggested minimum timeout: 20s. Make sure it's valid before you commit, fr fr. βœ…
  • meta-data β€” retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s. Behind-the-scenes icon behavior. 🫢

🧚 EXAMPLE CRM SHELL 🧚

Here's an example configuration for a drbd-attr resource using the crm(8) shell. Copy the vibe, keep the exact command:

primitive p_drbd-attr ocf:linbit:drbd-attr \
  op monitor timeout="20s" interval="60s" depth="0"

πŸ’œ EXAMPLE PCS πŸ’œ

And here's an example configuration for a drbd-attr resource using pcs(8):

pcs resource create p_drbd-attr ocf:linbit:drbd-attr \
  op monitor timeout="20s" interval="60s" depth="0"

πŸ”— SEE ALSO πŸ”—

Go read, bestie. The lore is there. 🌐

πŸ‘‘ AUTHORS πŸ‘‘

LINBIT HA Solutions GmbH β€” absolute legends. πŸ’–


This page is brought to you by drbd-pacemaker 9.34.0, dated 04/22/2026, and it's OCF_LINBIT_DRBD-ATT(7). Mwah, go be iconic with your DRBD events πŸ’…βœ¨

πŸ“¦ where this page comes from