nilfs_ioctl...blocks_dirty(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

nilfs_ioctl_mark_blocks_dirty β€” bestie, this one literally just marks blocks as dirty ✨


🌸 SYNOPSIS 🌸

int nilfs_ioctl_mark_blocks_dirty (struct the_nilfs *nilfs , struct
nilfs_argv *argv , void *buf );

πŸŽ€ ARGUMENTS πŸŽ€

  • nilfs β€” the nilfs object itself, the main character of this whole situation πŸ‘‘
  • argv β€” vector of arguments coming at us from userspace, iykyk
  • buf β€” array of block descriptors, the whole squad 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so nilfs_ioctl_mark_blocks_dirty does exactly what it says on the tin β€” it marks metadata file blocks or data blocks as dirty. no cap, that's the whole vibe check. πŸ’…


⭐ RETURN ⭐

On success you get back the number of processed block descriptors (slay, it tells you how many it handled). On failure you get one of these negative error codes, and it's giving sad girl hours 😭:

  • -EIO β€” I/O error πŸ”₯
  • -ENOENT β€” non-existent block (that's a hole block, literally not there πŸ™ˆ)
  • -ENOMEM β€” not enough memory available, the struggle πŸ’€
fr fr check the return value, bestie β€” negative means something went wrong and you should not just ignore it πŸ’œ

🌈 SEE ALSO 🌈

Kernel file ./fs/nilfs2/ioctl.c plus the whole friend group:


and that's the whole page, bestie 🧚 this cutie lives in the Kernel API Manual under ./fs/nilfs2, dated October 2026 β€” go forth and mark those blocks dirty, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from