drbd_rs_begin_io(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 drbd_rs_begin_io(9) 🌸

okay so bestie, welcome to the Kernel API Manual β€” this one's a little kernel function called drbd_rs_begin_io, and it's literally the moment a resync extent gets pulled into the resync LRU cache and marked as BME_LOCKED. locked in, literally. πŸ’…


✨ NAME ✨

drbd_rs_begin_io β€” gets an extent in the resync LRU cache and sets it to BME_LOCKED. that's the whole vibe. it grabs the extent, it locks it, it's done. πŸŽ€


✨ SYNOPSIS ✨

int drbd_rs_begin_io(struct drbd_device *device, sector_t sector);

✨ ARGUMENTS ✨

  • device β€” the DRBD device. your main character. 🫢
  • sector β€” the sector number. the address of the drama, iykyk. πŸ“

✨ DESCRIPTION ✨

so what actually happens? this function sleeps on al_wait. that's it, that's the tea. it goes night-night waiting on al_wait, no cap. πŸ˜΄πŸ’€


✨ RETURN ✨

  • 0 β€” success, we ate. πŸ“βœ¨
  • -EINTR β€” interrupted. rude, honestly. 😭

✨ SEE ALSO ✨

peep the kernel file ./drivers/block/drbd/drbd_actlog.c for the lore, plus these iconic siblings:

go read them, they're giving family reunion. πŸ‘‘


ok that's the whole page bestie, no gatekeeping here β€” ./drivers/block/drbd, dated October 2026, the drbd_rs_begin_io(9) era. mwah πŸ’‹πŸ¦‹ stay hydrated and don't forget to check your return values πŸ§šπŸ’œ
πŸ“¦ where this page comes from