is_block_dirty(9)
π is_block_dirty(9)
okay so bestie, welcome to the Kernel API Manual β¨ β yes, the actual kernel API manual, and yes, we're reading it together, because this little function is lowkey iconic and you're gonna get it in like thirty seconds. π«Ά
β¨ NAME β¨
is_block_dirty β check whether a recovery block is dirty π
πΈ SYNOPSIS πΈ
bool is_block_dirty (const struct recovery_journal_block *block );
π ARGUMENTS π
blockβ the block to check. that's it. that's the whole vibe check right there. π¦
π DESCRIPTION π
so like, this tells you whether the block has any uncommitted entries. and "uncommitted entries" is doing a lot of work here, bestie, because it means both:
- entries that were never written βοΈβ, and
- entries that were written but not yet acknowledged π
both of those count. no cap. π₯
π RETURN π
True if the block has any uncommitted entries. simple. clean. slayed. π
ngl this is the kind of function that just answers a yes/no question and then minds its own business. main character energy fr fr. π
π SEE ALSO π
okay this is the part where the manpage just dumps the entire cast of the recovery-journal cinematic universe on us and honestly? obsessed. π here's everybody, and yes, every single one of them appears on this list for real:
- Kernel file
./drivers/md/dm-vdo/recovery-journal.cLock 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_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)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 ππ
okay bye bestie, this page came from ./drivers/md/dm-vdo and it's dated October 2026 β so mark your calendar, hydrate, and go check some blocks π
πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms