vdo_get_jour...block_sector(9)

💖 NAME 💖

vdo_get_journal_block_sector - find the recovery journal sector from the block header and sector number. ✨

okay bestie, quick vibe check: this is the vdo_get_journal_block_sector page from the vdo_get_jour...block_sector(9) Kernel API Manual, and it’s literally here to help you find that recovery journal sector. 💅

---

🌸 SYNOPSIS 🌸

The signature, bestie — copy it exactly:

struct packed_journal_sector * vdo_get_journal_block_sector (struct
       packed_journal_header *header , int sector_number );

---

🎀 ARGUMENTS 🎀

• header — the header of the recovery journal block. 🫶
• sector_number — the index of the sector, and it’s 1-based. 👑

---

🦋 RETURN 🦋

A packed recovery journal sector. That’s the whole return value, periodt. ✨

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/md/dm-vdo/encodings.h — and here’s the whole reference squad, no skips, no cuts: 💖

• Block map entries(9)
• vdo_are_same_version(9)
• vdo_pack_version_number(9)
• vdo_unpack_version_number(9)
• vdo_pack_header(9)
• vdo_unpack_header(9)
• vdo_get_index_region_start(9)
• vdo_get_data_region_start(9)
• vdo_get_index_region_size(9)
• vdo_pack_recovery_journal_entry(9)
• vdo_unpack_recovery_journal_entry(9)
• vdo_is_valid_recovery_journal_sector(9)
• vdo_compute_recovery_journal_block_number(9)
• vdo_pack_recovery_block_header(9)
• vdo_unpack_recovery_block_header(9)
• vdo_compute_slab_count(9)
• vdo_get_saved_reference_count_size(9)
• vdo_get_slab_journal_start_block(9)
• vdo_advance_journal_point(9)
• vdo_before_journal_point(9)
• vdo_pack_journal_point(9)
• vdo_unpack_journal_point(9)
• vdo_pack_slab_journal_block_header(9)
• vdo_unpack_slab_journal_block_header(9)
• vdo_pack_slab_journal_entry(9)
• vdo_unpack_slab_journal_entry(9)
• vdo_get_slab_summary_hint_shift(9)

---

source/version: ./drivers/md/dm-vdo · date: October 2026 · manual: vdo_get_jour...block_sector(9) — mwah, bye bestie! 💋✨