vdo_get_reco...uence_number(9)

💅 vdo_get_recovery_journal_current_sequence_number(9)

okay so bestie, welcome to the Kernel API Manual ✨ (yes that's the manual name, we're in the kernel section now, put your seatbelt on 🎀). Today's main character is vdo_get_recovery_journal_current_sequence_number — the truncated header calls it vdo_get_reco...uence_number(9) because even the manpage header ran out of room, iconic honestly 😭.

---

🌸 NAME

vdo_get_recovery_journal_current_sequence_number — literally just goes and gets the recovery journal's current sequence number. that's it. that's the whole job. 🫶

---

✨ SYNOPSIS

sequence_number_t vdo_get_recovery_journal_current_sequence_number
(struct recovery_journal *journal );

like, you hand it a journal, it hands you back a sequence_number_t. simple trade. no cap 🔥

---

🦋 ARGUMENTS

• journal — the journal in question, babes. the one we're asking about. the main character journal, if you will 👑

---

💖 DESCRIPTION

okay this is the tea ☕: it's exposed only so the block map can be initialized therefrom.

that's the whole description fr fr — no extra lore, no side quests. the block map needs a number, this function is the one allowed to give it one. iykyk 🧚

---

⭐ RETURN

the sequence number of the tail block. that's what you get. slay 💅

---

🌈 SEE ALSO

okay so this list is LONG, grab a snack 🍓 — literally every one of these is a (9) and they're all chillin' in the kernel file ./drivers/md/dm-vdo/recovery-journal.c:

• Lock Counters.(9)
• get_zone_count_ptr(9)
• get_counter(9)
• is_journal_zone_locked(9)
• vdo_release_recovery_journal_block_reference(9)
• pop_free_list(9)
• is_block_dirty(9)
• is_block_empty(9)
• is_block_full(9)
• assert_on_journal_thread(9)
• continue_waiter(9)
• has_block_waiters(9)
• suspend_lock_counter(9)
• check_for_drain_complete(9)
• notify_recovery_journal_of_read_only_mode(9)
• enter_journal_read_only_mode(9)
• get_recovery_journal_head(9)
• compute_recovery_count_byte(9)
• check_slab_journal_commit_threshold(9)
• finish_reaping(9)
• complete_reaping(9)
• handle_flush_error(9)
• initialize_journal_state(9)
• vdo_get_recovery_journal_length(9)
• reap_recovery_journal_callback(9)
• initialize_lock_counter(9)
• set_journal_tail(9)
• initialize_recovery_block(9)
• vdo_decode_recovery_journal(9)
• vdo_free_recovery_journal(9)
• vdo_initialize_recovery_journal_post_repair(9)
• vdo_get_journal_block_map_data_blocks_used(9)
• vdo_get_recovery_journal_thread_id(9)
• vdo_open_recovery_journal(9)
• vdo_record_recovery_journal(9)
• get_block_header(9)
• set_active_sector(9)
• advance_tail(9)
• initialize_lock_count(9)
• prepare_to_assign_entry(9)
• schedule_block_write(9)
• release_journal_block_reference(9)
• assign_entry(9)
• recycle_journal_block(9)
• continue_committed_waiter(9)
• notify_commit_waiters(9)
• recycle_journal_blocks(9)
• complete_write(9)
• add_queued_recovery_entries(9)
• write_block(9)
• write_blocks(9)
• vdo_add_recovery_journal_entry(9)
• is_lock_locked(9)
• reap_recovery_journal(9)
• vdo_acquire_recovery_journal_block_reference(9)
• vdo_release_journal_entry_lock(9)
• vdo_drain_recovery_journal(9)
• resume_lock_counter(9)
• vdo_resume_recovery_journal(9)
• vdo_get_recovery_journal_logical_blocks_used(9)
• vdo_get_recovery_journal_statistics(9)
• dump_recovery_block(9)
• vdo_dump_recovery_journal_statistics(9)

like… that's the whole friend group 😭🫶

---

ngl bestie, this one's a tiny page but it's doing exactly what it says on the tin — no lore, no plot twists, just a sequence number of the tail block. periodt. 💜

---

🎀 and that's a wrap! this one came out of the ./drivers/md/dm-vdo source, dated October 2026, and the header/footer kept yelling vdo_get_reco...uence_number(9) at us the whole time — bye bestie, go initialize that block map 💖✨🌷