DRBD-RECONFIGURE-S(7)

💖 DRBD-RECONFIGURE-S(7) 💖

okay bestie, so this one lives in the DRBD Manual, and its whole personality is: system unit that re-configures specific DRBD aspects. that's it, that's the job. ✨

---

🎀 NAME 🎀

drbd-reconfigure-suspend-or-error@.service — a System unit to re-configure specific DRBD aspects. no cap, that's literally what it does. 🫶

---

🌸 SYNOPSIS 🌸

drbd-reconfigure-suspend-or-error@RESNAME.service

---

✨ DESCRIPTION ✨

so here's the tea, bestie. if a disk fails, or a replication link just 🪦 goes down, and as a consequence DRBD loses "quorum" or access to good data, DRBD can be configured to do one of two things: suspend-io, or return io-errors.

io-errors let file systems and applications notice and stop themselves, or get unmounted. the whole assumption here is that some other node(s) will still have good data, and some cluster manager or other monitoring entity will notice the situation and try to bring up services over there. main character energy for the other node, honestly. 👑

suspend-io lets the problematic incident be hidden from file systems and applications — they'd just block until access to good data is restored. this can be useful to cope with supposedly short "network hickup" type incidents without causing service restarts. it's giving "pretend nothing happened" and honestly sometimes that works. 🙈

but — and this is the important part, so listen up — if IO is "suspended" (blocked, frozen, also known as "un-interruptible sleep" or "D state"), applications cannot be killed, and file systems cannot be unmounted. 💀 like, at all.

and if some other node was told to take over services meanwhile, we need to demote DRBD on the "frozen" node before we can re-integrate it. so that's a whole situation.

in these scenarios it may be useful to configure DRBD for suspend-io during normal operation, so it would mask intermittent problems — but if services had been taken over by some other partition of nodes in the storage cluster, reconfigure for io-error, to be able to bring down services and unmount file systems before trying to re-integrate this node. slay. 💅

so this service does the switch-hitting: it reconfigures RESNAME for suspend-io when started, and for io-error when stopped. iconic behaviour, truly.

⚠️ bestie, listen: you should test a lot and maybe talk to LINBIT support before using this. like, actually. don't just yolo it into prod. 😭

also see the DRBD User’s Guide[1] — link's down in NOTES. 🦋

---

👑 AUTHORS 👑

LINBIT HA Solutions GmbH https://linbit.com

---

📝 NOTES 📝

1. DRBD User’s Guide https://linbit.com/drbd-user-guide/drbd-guide-9_0-en/

---

and that's the whole page, bestie! this one's from drbd-utils, dated 2026-08-15, and you just read DRBD-RECONFIGURE-S(7). go forth and reconfigure responsibly. 💖✨🎀