ubifs_recover_size_accum(9)

✨ ubifs_recover_size_accum ✨

okay so bestie, welcome to the glow-up of ubifs_recover_size_accum(9) — that's the kernel API manual page for this little UBIFS recovery helper 💅 literally the whole vibe is "accumulate inode sizes for recovery" and honestly? iconic.

---

🌸 SYNOPSIS 🌸

int ubifs_recover_size_accum (struct ubifs_info *c , union ubifs_key
*key , int deletion , loff_t new_size );

that's the whole signature, fr fr — copy it exactly, no cap 🫶

---

🎀 ARGUMENTS 🎀

• c — the UBIFS file-system description object 💖 like, the whole fs's little profile card
• key — the node key 🔑
• deletion — this node is for a deletion 🗑️ (yes queen, it's a deletion)
• new_size — the inode size 📏

---

🦋 DESCRIPTION 🦋

okay so this function has two purposes, and they're both lowkey doing the most for the integrity of your file system:

1. to ensure there are no data nodes that fall outside the inode size 🧐
2. to ensure there are no data nodes for inodes that do not exist 👻

to accomplish those purposes, a rb-tree is constructed containing an entry for each inode number in the journal that has not been deleted, and recording the size from the inode node, the maximum size of any data node (also altered by truncations) and a flag indicating a inode number for which no inode node was present in the journal. 🌈 it's giving red-black tree main character energy, honestly

note that there is still the possibility that there are data nodes that have been committed that are beyond the inode size, however the only way to find them would be to scan the entire index. alternatively, some provision could be made to record the size of inodes at the start of commit, which would seem very cumbersome for a scenario that is quite unlikely and the only negative consequence of which is wasted space. 😭 so like… yeah. it's a tradeoff, bestie. wasted space is the worst-case, and that's it.

this functions returns 0 on success and a negative error code on failure. ✨ no cap, that's the whole return contract

---

💜 SEE ALSO 💜

kernel file ./fs/ubifs/recovery.c is the home base, and these are all the siblings you should also go stan:

• is_empty(9)
• first_non_ff(9)
• get_master_node(9)
• write_rcvrd_mst_node(9)
• ubifs_recover_master_node(9)
• ubifs_write_rcvrd_mst_node(9)
• is_last_write(9)
• clean_buf(9)
• no_more_nodes(9)
• fix_unclean_leb(9)
• drop_last_group(9)
• drop_last_node(9)
• ubifs_recover_leb(9)
• get_cs_sqnum(9)
• ubifs_recover_log_leb(9)
• recover_head(9)
• ubifs_recover_inl_heads(9)
• clean_an_unclean_leb(9)
• ubifs_clean_lebs(9)
• grab_empty_leb(9)
• ubifs_rcvry_gc_commit(9)
• struct size_entry(9)
• add_ino(9)
• find_ino(9)
• remove_ino(9)
• ubifs_destroy_size_tree(9)
• fix_size_in_place(9)
• inode_fix_size(9)
• ubifs_recover_size(9)

---

okay that's the whole page, bestie — go forth and recover those sizes 💅✨

cute sign-off time 🎀: this one lives in ./fs/ubifs, dated October 2026, and yes those are literally the manual's own source and date, I'm not making it up 🫶