recover_local_statfs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… recover_local_statfs(9) πŸ’…

okay bestie, welcome to the Kernel API Manual entry for recover_local_statfs(9) β€” this one is lowkey all about keeping statfs changes in sync during recovery, and yes, it ate. ✨


🌸 NAME 🌸

recover_local_statfs β€” update the master and local statfs changes for this journal. that's the whole vibe. πŸ’–


✨ SYNOPSIS ✨

void recover_local_statfs (struct gfs2_jdesc *jd , struct
gfs2_log_header_host *head );

πŸŽ€ ARGUMENTS πŸŽ€

  • jd β€” the journal. πŸ““
  • head β€” the journal head. πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the lore, bestie. Previously, statfs updates would be read in from the local statfs inode and synced to the master statfs inode during recovery. that was the old way.

now? we use the statfs updates in the journal head to update the master statfs inode instead of reading in from the local statfs inode. iconic behavior, honestly. πŸ’…

but plot twist: to preserve backward compatibility with kernels that can't do this, we still need to keep the local statfs inode up to date by writing changes to it. literally required. no cap. πŸ”₯

at some point in the future, we can do away with the local statfs inodes altogether and keep the statfs changes solely in the journal. future vibes. 🌈


🌟 RETURN 🌟

the return value is errno. that's it. that's the return. 🫢


πŸ’œ SEE ALSO πŸ’œ

Kernel file ./fs/gfs2/recovery.c: get_log_header(9), foreach_descriptor(9), clean_journal(9), update_statfs_inode(9).


πŸ«ΆπŸ’– that's the page, bestie! source/version: ./fs/gfs2 β€’ date: October 2026 β€’ recover_local_statfs(9) β€” bye, mwah πŸ’‹βœ¨
πŸ“¦ where this page comes from