check_inodes(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 check_inodes β€” checks all inodes 🌸

okay so this one is from the Kernel API Manual, section 9 β€” yes, the big-kid kernel section, we love that for us 🫢


✨ NAME ✨

check_inodes β€” literally just checks all the inodes. that's the whole job. she's a very "no thoughts head empty just verify" icon πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

int check_inodes (struct ubifs_info *c , struct fsck_data *fsckd );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • c β€” the UBIFS file-system description object. the whole vibe of the filesystem lives in here πŸ—‚οΈ
  • fsckd β€” the FS checking information. all the fsck-y deets go in this one πŸ“‹

πŸ”₯ DESCRIPTION πŸ”₯

okay so picture this: this is a helper function for dbg_check_filesystem, right? and what she does is she walks the RB-tree of inodes after the index scan has finished. like, the scan is done, everybody's seated, and now she's doing the vibe check ✨

and what's she checking? that inode nlink, size, etc. are correct. the etc. is doing a lot of heavy lifting there but that's what the manpage says so we're saying it too, no cap πŸ’€

Returns:

  • zero if the inodes are fine β€” slay, we love a clean run 🌈
  • -EINVAL if they're not fine β€” not slay, something's wrong 😭
  • a negative error code in case of failure β€” like an actual "something broke broke" failure, not just a "validation failed" failure πŸ™ˆ
bestie please note: "returns zero if inodes are fine, -EINVAL if not, and a negative error code in case of failure" β€” those are three separate outcomes, don't merge them in your head, i'm begging 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./fs/ubifs/debug.c β€” and the whole friend group, in the order the manpage gives them:


that's the whole page, bestie, you ate it up πŸ“βœ¨ from ./fs/ubifs, dated October 2026 β€” mwah, see you in the next manpage πŸ’–πŸŽ€

πŸ“¦ where this page comes from