copy_partition(9)

💖 copy_partition(9) — Kernel API Manual 💖

Okay bestie, welcome to the <pink>copy_partition(9)</pink> page from the <purple>Kernel API Manual</purple> 💅 This one is short, sweet, and very “trust the process” energy.

✨ NAME ✨

copy_partition — bestie, this copies a partition from the location specified in the current layout over to that in the next layout. Slay. 🎀

🌸 SYNOPSIS 🌸

void copy_partition (struct vdo *vdo , enum partition_id id , struct
vdo_completion *parent );

🔥 ARGUMENTS 🔥

• vdo — the vdo that’s preparing to grow 💖
• id — the ID of the partition to copy 🦋
• parent — the completion to notify when the copy is complete 🫶

👀 SEE ALSO 👀

First up, the linked kernel file is literally right here: ./drivers/md/dm-vdo/dm-vdo-target.c ✨

And the whole SEE ALSO squad, no cap:

• free_device_config(9)
• get_version_number(9)
• parse_bool(9)
• parse_memory(9)
• parse_slab_size(9)
• process_one_thread_config_spec(9)
• parse_one_thread_config_spec(9)
• parse_thread_config_string(9)
• process_one_key_value_pair(9)
• parse_one_key_value_pair(9)
• parse_key_value_pairs(9)
• parse_optional_arguments(9)
• handle_parse_error(9)
• parse_device_config(9)
• get_thread_id_for_phase(9)
• advance_phase(9)
• finish_operation_callback(9)
• decode_from_super_block(9)
• decode_vdo(9)
• pre_load_callback(9)
• get_bit_array_size(9)
• grow_bit_array(9)
• allocate_instance(9)
• check_may_grow_physical(9)
• grow_layout(9)
• validate_new_device_config(9)
• write_super_block_for_suspend(9)
• suspend_callback(9)
• was_new(9)
• requires_repair(9)
• get_load_type(9)
• load_callback(9)
• handle_load_error(9)
• write_super_block_for_resume(9)
• resume_callback(9)
• grow_logical_callback(9)
• handle_logical_growth_error(9)
• perform_grow_logical(9)
• grow_physical_callback(9)
• handle_physical_growth_error(9)
• perform_grow_physical(9)
• apply_new_vdo_configuration(9)

💌 Sign-off time, bestie: this page’s source/version is ./drivers/md/dm-vdo, and the date on it is October 2026. Bye, love you, mwah! 🫶💋