vdo_drain_recovery_journal(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– vdo_drain_recovery_journal(9) πŸ’–

okay so we're in the Kernel API Manual bestie, and this page is all about vdo_drain_recovery_journal β€” literally Drain recovery journal I/O. no cap.


✨ NAME ✨

vdo_drain_recovery_journal β€” Drain recovery journal I/O. that's the whole vibe. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

void vdo_drain_recovery_journal (struct recovery_journal *journal ,
const struct admin_state_code *operation , struct vdo_completion *parent
);

πŸ’… ARGUMENTS πŸ’…

  • journal β€” the journal to drain. that's the main character of this little operation. πŸ‘‘
  • operation β€” the drain operation, and it's giving either suspend or save. pick your fighter. ✨
  • parent β€” the completion to notify once the journal is drained. like, "hey bestie, we're done here" 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

All uncommitted entries will be written out. periodt. not a single uncommitted entry is getting left behind on this watch. πŸ’–


🌈 SEE ALSO 🌈

if you wanna go down the cross-reference rabbit hole πŸ•³οΈ here's the whole squad, every single one β€” don't skip anybody:


okay that's the whole page, bestie 🫢 β€” this cutie is filed under ./drivers/md/dm-vdo and dated October 2026. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from