nilfs_cpfile...e_checkpoint(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, welcome to the Kernel API Manual page for nilfs_cpfile_create_checkpoint β€” the function that creates a checkpoint entry on cpfile. The page header has a little truncation situation going on β€” nilfs_cpfile...e_checkpoint(9) β€” but the function name is the full glow-up above. ✨


✨ SYNOPSIS ✨

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

🫢 ARGUMENTS 🫢

  • cpfile β€” checkpoint file inode. it's the inode holding the checkpoint file, periodt.
  • cno β€” number of checkpoint to set up. literally the checkpoint number you want to create.

πŸ’… DESCRIPTION πŸ’…

okay so here's the tea: this function creates a checkpoint with the number specified by cno on cpfile. If the specified checkpoint entry already exists due to a past failure, it will be reused without returning an error β€” no cap, that's a reuse situation, not an error situation. In either case, the buffer of the block containing the checkpoint entry and the cpfile inode are made dirty for inclusion in the write log. highkey important. πŸ’–


πŸ”₯ RETURN πŸ”₯

0 on success, or one of the following negative error codes on failure:

  • -ENOMEM β€” Insufficient memory available.
  • -EIO β€” I/O error (including metadata corruption).
  • -EROFS β€” Read only filesystem.

🌈 SEE ALSO 🌈

Kernel file ./fs/nilfs2/cpfile.c β€” and the whole bestie squad:


byeee πŸ’– this page is from ./fs/nilfs2, dated October 2026 β€” mwah, go make that checkpoint entry iconic! πŸŽ€

πŸ“¦ where this page comes from