nilfs_cpfile...e_checkpoint(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nilfs_cpfile_delete_checkpoint(9) — the Kernel API Manual moment ✨

okay so bestie, welcome to the nilfs_cpfile...e_checkpoint(9) page from the Kernel API Manual 🎀 — yes that title is truncated, no I don't know why, yes we're moving on. this is the whole vibe: one function, one job, deleting a checkpoint. slay.

✨ NAME ✨

nilfs_cpfile_delete_checkpoint — literally just deletes a checkpoint. that's it. that's the whole function 💅

🦋 SYNOPSIS 🦋

int nilfs_cpfile_delete_checkpoint (struct inode *cpfile , __u64 cno );

look at her. iconique. note the lil space before the comma in *cpfile , — that's not a typo on my part, that's canon, we keep it exactly as-is, no cap 🫶

🌸 ARGUMENTS 🌸

  • cpfile — the checkpoint file inode. yes it's a struct inode *, yes it's the cpfile one, she's the main character here 👑
  • cno — the checkpoint number you wanna delete, as a __u64. pick your victim, bestie 🎯

💖 RETURN 💖

she returns 0 on success ✨ — and on failure she hits you with one of these negative error codes, in list form because we're organized:

  • -EBUSY — checkpoint is in use (snapshot specified). so like, it's taken, back off 🙈
  • -EIO — I/O error, and yes that includes metadata corruption 😭 things are Not Okay
  • -ENOENT — no valid checkpoint found. she looked. there was nothing there. 💀
  • -ENOMEM — insufficient memory available. the vibes ran out of RAM 🍓
lowkey if you get -EIO with metadata corruption in the mix, that's your cue to actually pay attention, bestie. not a drill 💜

⭐ SEE ALSO ⭐

kernel file ./fs/nilfs2/cpfile.c, and honestly the whole friend group:

periodt. go read them, they're all right there 🧚

and that's the page!! mwah 💋 this little number lives in ./fs/nilfs2, dated October 2026, and it goes by nilfs_cpfile...e_checkpoint(9) forever and always 🌈 🎀

📦 where this page comes from