vdo_record_recovery_journal(9)

🎀 vdo_record_recovery_journal(9) 🎀

okay so bestie, welcome to vdo_record_recovery_journal(9) — yes that's the whole name, it's a mouthful, we deal 💅 this is a Kernel API Manual page and it's honestly short and sweet, so let's get into it ✨

---

🌸 NAME 🌸

vdo_record_recovery_journal — the way it literally grabs the state of a recovery journal so it can be encoded in the super block. that's the whole job. iconic. no cap 💖

---

🦋 SYNOPSIS 🦋

struct recovery_journal_state_7_0 vdo_record_recovery_journal (const
struct recovery_journal *journal );

like, yes, that's the whole signature. look at that struct recovery_journal_state_7_0 return type sitting there being all main character energy 👑

---

🌈 ARGUMENTS 🌈

• journal — the recovery journal. that's it. that's the argument. she takes the journal and nothing else 🫶

---

⭐ RETURN ⭐

it hands you back the state of the journal. that's the tea, that's the whole return value 🍓

---

💜 SEE ALSO 💜

okay this list is LONG, buckle up bestie, we are listing every single one because nobody gets left behind fr fr 😭

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_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), 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 a lot of friends. she's connected. iykyk 🔥

---

ngl there's not a single warning, bug note, exit status or default value in this whole page — it's a short one and that's the vibe check result. every fact from the original is up there, we did NOT skip a thing 💀✨

---

and that's the page, bestie!! written from the ./drivers/md/dm-vdo source, version vibes of October 2026, and no we will not be normal about a two-argument kernel function 🎀💖🦋💅