drbd_try_rs_begin_io(9)
hii bestie π you're reading the Kernel API Manual entry for drbd_try_rs_begin_io(9), and it's a whole little vibe. it gets an extent in the resync LRU cache, and it does not sleep. no cap. π
β¨ NAME β¨
drbd_try_rs_begin_io β Gets an extent in the resync LRU cache, does not sleep. periodt πΈ
π¦ SYNOPSIS π¦
int drbd_try_rs_begin_io (struct drbd_peer_device *peer_device ,
sector_t sector );
π ARGUMENTS π
peer_deviceβ DRBD device. like, the DRBD device we're working with π«Άsectorβ the sector number. yep, that exact sector π«
π DESCRIPTION π
so here's the vibe: it gets an extent in the resync LRU cache, sets that extent to BME_NO_WRITES, and then tries to set it to BME_LOCKED. that's the little sequence, bestie. and yes, it does not sleep β no bedtime here π΄π«
π₯ RETURN π₯
0upon success β slay β-EAGAINif there is still application IO going on in this area β so if application IO is still happening there, you get-EAGAIN, periodt π
π SEE ALSO π
Kernel file ./drivers/block/drbd/drbd_actlog.c β go peek if you're nosy π
k bye bestie π this page came from ./drivers/block/drbd, dated October 2026, and it's the manual entry for drbd_try_rs_begin_io(9). mwah π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms