vdo_save_components(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

vdo_save_components(9) πŸ’…βœ¨

okay so bestie, this is the Kernel API Manual page for vdo_save_components(9), and it’s lowkey iconic. 🫢 No cap: it’s all about the VDO state and saving it off asynchronously.


✨ NAME ✨

vdo_save_components β€” copy the current state of the VDO to the states struct and save it to the super block asynchronously. It’s giving β€œsave the components, but make it background vibe” πŸ’–

🌸 SYNOPSIS 🌸

void vdo_save_components (struct vdo *vdo , struct vdo_completion
       *parent );

πŸŽ€ ARGUMENTS πŸŽ€

  • vdo β€” the vdo whose state is being saved. Yes, that vdo. The one with the state. πŸ’…
  • parent β€” the completion to notify when the save is complete. Like, it gets the little β€œdone bestie” signal. πŸ””

πŸ¦‹ SEE ALSO πŸ¦‹

okay, grab a snack, because this list is long but every single ref is here, fr fr:


mwah πŸ’‹ source/version: ./drivers/md/dm-vdo Β· date: October 2026 Β· page: vdo_save_components(9). That’s the footer, bestie β€” go save those components and slay. πŸ‘‘βœ¨

πŸ“¦ where this page comes from