vdo_get_rec...block_number(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

vdo_get_recovery_journal_block_number β€” bestie, this one hands you the physical block number for a given sequence number. that's it, that's the whole vibe ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

physical_block_number_t vdo_get_recovery_journal_block_number (const
struct recovery_journal *journal , sequence_number_t sequence );

okay so quick note: this page is straight out of the Kernel API Manual, so you already know it's giving serious kernel-dev energy πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • journal β€” the journal itself πŸ’– literally just the journal, that's the whole description, no notes.
  • sequence β€” the sequence number of the block you're obsessed with. like, the block you want. 🫢

⭐ RETURN ⭐

it returns the block number that corresponds to that sequence number. periodt. no cap, that's the entire return value πŸ”₯


🌸 SEE ALSO 🌸


okay bestie that's the whole page, you ate that πŸ“ this lil slice of the kernel lives in ./drivers/md/dm-vdo, and it's dated October 2026 β€” so go forth and get those block numbers, iykyk πŸ’€πŸ’…πŸŒˆ

πŸ“¦ where this page comes from