STRUCT NILFS_FINFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct nilfs_finfo(9) πŸ’–

okay bestie, so we're in the Kernel API Manual today and the whole vibe is this lil struct called nilfs_finfo β€” it's literally just file information and nothing more. no cap. πŸŽ€


✨ SYNOPSIS ✨

here's the whole thing, look at her go πŸ‘‘

struct nilfs_finfo {
    __le64 fi_ino;
    __le64 fi_cno;
    __le32 fi_nblocks;
    __le32 fi_ndatablk;
 };

that's it. that's the struct. she's compact, she's tidy, she's iconic. πŸ’…


🌸 Members 🌸

okay so let's meet the members, they all carry their own lil job and honestly? they ate. 🫢

  • fi_ino β€” the inode number. that's her whole personality fr fr. πŸ¦‹
  • fi_cno β€” the checkpoint number. the way that this is just tracking checkpoints… obsessed. ✨
  • fi_nblocks β€” the number of blocks, and yes that includes the intermediate blocks too, don't forget those bestie, they count. πŸ”₯
  • fi_ndatablk β€” the number of file data blocks. data blocks specifically. don't get it twisted. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

like, go read these too, they're all in the same friend group:

Kernel file ./include/uapi/linux/nilfs2_ondisk.h

  • struct nilfs_inode(9)
  • struct nilfs_super_root(9)
  • struct nilfs_super_block(9)
  • struct nilfs_binfo_v(9)
  • struct nilfs_binfo_dat(9)
  • union nilfs_binfo(9)
  • struct nilfs_segment_summary(9)
  • struct nilfs_btree_node(9)
  • struct nilfs_direct_node(9)
  • struct nilfs_palloc_group_desc(9)
  • struct nilfs_dat_entry(9)
  • struct nilfs_snapshot_list(9)
  • struct nilfs_checkpoint(9)
  • struct nilfs_cpfile_header(9)
  • struct nilfs_segment_usage(9)
  • struct nilfs_sufile_header(9)

that's the whole squad, no skips, we respect all of them. 🌈


🧚 friendly reminder: every one of those flags, numbers and names above is exactly as written β€” don't go renaming anything, that's not the vibe.

and that's the page bestie!! 🌸 this lil beauty lives in ./include/uapi/linux and the date on it is October 2026, and it's still filed under struct nilfs_finfo(9) obviously. mwah, bye, go read some source πŸ’œπŸŽ€

πŸ“¦ where this page comes from