nilfs_ioctl_sync(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nilfs_ioctl_sync(9) — Kernel API Manual, but make it cute: “make a checkpoint” ✨

🌸 NAME 🌸

okay so bestie, nilfs_ioctl_sync is literally the function that makes a checkpoint. That’s the whole name, no cap. 🎀

✨ SYNOPSIS ✨

the signature is giving:

int nilfs_ioctl_sync (struct inode *inode , struct file *filp , unsigned
       int cmd , void __user *argp );

🦋 ARGUMENTS 🦋

  • inode — the inode object. yes, that one. 💅
  • filp — the file object. 🫶
  • cmd — the ioctl’s request code. ⭐
  • argp — pointer on argument from userspace. 🌈

💖 DESCRIPTION 💖

So nilfs_ioctl_sync constructs a logical segment for checkpointing. The way it works is lowkey iconic: this function guarantees that all modified data and metadata are written out to the device when it successfully returned. Yes bestie — all of it, data and metadata, both. 💅✨ That guarantee is the main character energy of this whole function.

🔥 RETURN 🔥

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

  • -EFAULT — Failure during execution of requested operation.
  • -EIO — I/O error.
  • -ENOMEM — Insufficient memory available.
  • -ENOSPC — No space left on device (only in a panic state).
  • -ERESTARTSYS — Interrupted.
  • -EROFS — Read only filesystem.

🎀 SEE ALSO 🎀

Kernel file ./fs/nilfs2/ioctl.c is in the chat, and these besties are linked too: 🧚

Bye bestie 🫶 — this page comes from the Kernel API Manual, source ./fs/nilfs2, dated October 2026, and it’s all about nilfs_ioctl_sync(9). 💖

📦 where this page comes from