drbd_get_max_capacity(9)

💅 drbd_get_max_capacity(9) 💅

okay bestie, welcome to the Kernel API Manual — yes it's a real man page, yes it's about the DRBD kernel driver, and yes we're gonna make it make sense 🫶

---

✨ NAME ✨

drbd_get_max_capacity — literally returns the capacity we announce to our peer 💖 (the original says "out peer", which is a whole mood, but you get it — it's the peer)

---

🌸 SYNOPSIS 🌸

sector_t drbd_get_max_capacity (struct drbd_backing_dev *bdev );

no cap, that's the whole signature. one function, one pointer, one sector_t coming back atcha ✨

---

🎀 ARGUMENTS 🎀

• bdev — the meta data block device. that's it, that's the argument 🦋

---

💫 DESCRIPTION 💫

so the way this works: it returns the capacity we announce to our peer. simple, iconic, main character energy 👑

but here's the part where you gotta pay attention — we clip ourselves at the various MAX_SECTORS. why?? because if we don't, the current implementation will oops sooner or later 💀

not me being dramatic — that's literally what the page says. no clipping = oops. the kernel will absolutely throw hands. so we clip, we stay safe, we slay 🌈

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/block/drbd/drbd_int.h
• drbd_chk_io_error(9)
• drbd_md_first_sector(9)
• drbd_md_last_sector(9)
• drbd_md_ss(9)

go read those too, they're lowkey all in the same friend group 🧚

---

⭐ sign-off ⭐

this whole thing lives in ./drivers/block/drbd, it's dated October 2026, and it's from the Kernel API Manual. periodt 💅✨