OSTREE-FSCK(1)
π OSTREE-FSCK β check the repo for consistency, bestie
okay so this is ostree-fsck, straight out of the ostree manual (section 1, the classic). no cap, it's the vibe-check tool for your repository.
β¨ SYNOPSIS β¨
ostree fsck [OPTIONS...]
like, that's it. you summon it, you optionally hand it some flags, it goes to work. slay.
π«Ά DESCRIPTION π«Ά
so what does it actually do? it checks the repository to verify the content integrity of commit objects π β basically it's the friend who goes through your whole closet and is like "girl, this is fine, but this? corrupted."
it looks for missing and corrupted objects and metadata, and it validates the directory structure and metadata too. so it's giving full-body scan, not just a wink in the mirror. it's thorough, it's iconic, it does not skip.
π OPTIONS π
--quiet,-qβ shhh π€« only print error messages. everything else stays in the group chat drafts. perfect when you just want the drama (errors) and not the play-by-play.--deleteβ remove corrupted objects. yes, remove. it's the "throw it out, we're starting over" option π so, like, know what you're doing before you use it.--add-tombstonesβ adds a tombstone commit for referenced but missing commits. headstone for a commit that got ghosted πͺ¦ referenced, but not actually there.--verify-bindingsβ verifies that the commits pointed to by each ref have that ref in the binding set. and bestie, listen: you should usually add this option. it only defaults to off for backwards compatibility. so it's not being shady, it's just being polite to old repos. π--verify-back-refsβ verifies that all the refs listed in a commit's ref-bindings point to that commit. the reverse check, the "are we mutuals?" check π but heads up β this cannot be used in repositories where the target of refs is changed over time as new commits are added. it can be used in repositories which are regenerated from scratch for each commit. also, it implies--verify-bindingsas well. package deal π
π EXAMPLE π
$ ostree fsck
Enumerating objects...
Verifying content integrity of of 2 commit objects
0/2572 objects
2571/2572 objects
look at it go π counting objects like a responsible main character. (and yes, the "of of" is really in the original β we respect the typo, we don't fix the typo. iykyk π )
β reminder that the internals here are exactly as written β don't go "correcting" the output strings, okay? character for character, periodt.
okay that's the whole page!! π¦ this one came from the OSTree source, dated in the footer, and it's OSTREE FSCK(1) all the way down β mwah π thanks for reading, go check your repo, love u bye π«Άβ¨
π¦ where this page comes from
- arch rolling: ostree 2026.6-1 Β· LGPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms