nilfs_cpfile_change_cpmode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

nilfs_cpfile_change_cpmode β€” change checkpoint mode. This page is from the Kernel API Manual, and yes bestie, we’re changing a checkpoint mode today. πŸ’…

✨ SYNOPSIS ✨

int nilfs_cpfile_change_cpmode (struct inode *cpfile , __u64 cno , int
       mode );

πŸŽ€ ARGUMENTS πŸŽ€

  • cpfile β€” inode of checkpoint file πŸ—‚οΈ
  • cno β€” checkpoint number πŸ”’
  • mode β€” mode of checkpoint πŸŽ›οΈ

πŸ’… DESCRIPTION πŸ’…

okay so nilfs_change_cpmode changes the mode of the checkpoint specified by cno. (Not me clocking that the name in this sentence is nilfs_change_cpmode while the page title is nilfs_cpfile_change_cpmode β€” I’m just relaying the lore, don’t shoot the messenger πŸ˜­πŸ’€.)

The mode value is NILFS_CHECKPOINT or NILFS_SNAPSHOT. That’s the whole vibe check: checkpoint mode in, checkpoint mode changed. ✨

πŸ”₯ RETURN πŸ”₯

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

  • -EIO β€” I/O error (including metadata corruption). πŸ’€
  • -ENOENT β€” No such checkpoint. πŸ™ˆ
  • -ENOMEM β€” Insufficient memory available. 😭

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./fs/nilfs2/cpfile.c and these iconic little references, all of them, no cap:


that’s the whole page, bestie β€” source stamp ./fs/nilfs2, date October 2026, for nilfs_cpfile_change_cpmode(9). go forth and change those checkpoint modes responsibly πŸ«ΆπŸ’–πŸŒˆ

πŸ“¦ where this page comes from