vdo_compute...block_number(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_compute_recovery_journal_block_number(9) πŸ’…

okay so we're in the Kernel API Manual bestie, welcome to the dm-vdo department of the kernel, it's giving very niche very iconic πŸŽ€


✨ NAME ✨

vdo_compute_recovery_journal_block_number β€” literally computes the physical block number of the recovery journal block that would have a given sequence number 🫢

🌸 SYNOPSIS 🌸

physical_block_number_t vdo_compute_recovery_journal_block_number
(block_count_t journal_size , sequence_number_t sequence_number );

like, that's the whole signature, no cap πŸ”₯

πŸ¦‹ ARGUMENTS πŸ¦‹

  • journal_size β€” the size of the journal, periodt. that's the vibe, that's the value πŸ’«
  • sequence_number β€” the sequence number. yeah bestie that's it, that's the argument 🌈

πŸ‘‘ RETURN πŸ‘‘

it hands you back the pbn of the journal block which would the specified sequence number πŸ’– (yes that's exactly what the original says and we're not editing the lore ngl)

🧚 SEE ALSO 🧚

Kernel file ./drivers/md/dm-vdo/encodings.h, and like, the entire extended universe of related functions, all of them, in this exact order, slay ⭐


ngl this one is a little short but she's still main character energy, don't underestimate her πŸ’…

okay that's the whole page, love u, go read encodings.h πŸ“

β€” sourced straight from ./drivers/md/dm-vdo, dated October 2026, mwah πŸ˜­πŸ’œ

πŸ“¦ where this page comes from