is_block_dirty(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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:

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