vdo_decode_recovery_journal(9)

🎀 vdo_decode_recovery_journal(9) — Kernel API Manual 🎀

okay so bestie, welcome to the Kernel API Manual moment for vdo_decode_recovery_journal(9). This is the one that makes a recovery journal and initializes it with the state that was decoded from the super block. It’s giving “set up the journal era,” and we’re gonna keep every single detail, no cap. 💅

✨ NAME ✨

vdo_decode_recovery_journal — make a recovery journal and initialize it with the state that was decoded from the super block.

🌸 SYNOPSIS 🌸

int vdo_decode_recovery_journal (struct recovery_journal_state_7_0 state
       , nonce_t nonce , struct vdo *vdo , struct partition *partition , u64
       recovery_count , block_count_t journal_size , struct recovery_journal
       **journal_ptr );

🦋 ARGUMENTS 🦋

• state — the decoded state of the journal. Already decoded, bestie — don’t re-decode it.
• nonce — the nonce of the VDO.
• vdo — the VDO.
• partition — the partition for the journal.
• recovery_count — the VDO’s number of completed recoveries.
• journal_size — the number of blocks in the journal on disk.
• journal_ptr — the pointer to hold the new recovery journal.

⭐ RETURN ⭐

A success or error code. That’s the whole return vibe.

🔥 SEE ALSO 🔥

bestie, this is the full cast list, and yes, every single one is here — no skipping. 🫶

• 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)
• vdo_get_recovery_journal_current_sequence_number(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_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)

— that’s the page, bestie. source/version: ./drivers/md/dm-vdo · date: October 2026 · manual page: vdo_decode_recovery_journal(9) 💖