{ "mode": "man", "parameter": "GIT-FSCK", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/GIT-FSCK/1/json", "generated": "2026-06-03T01:36:39Z", "synopsis": "git fsck [--tags] [--root] [--unreachable] [--cache] [--no-reflogs]\n[--[no-]full] [--strict] [--verbose] [--lost-found]\n[--[no-]dangling] [--[no-]progress] [--connectivity-only]\n[--[no-]name-objects] [*]", "sections": { "NAME": { "content": "git-fsck - Verifies the connectivity and validity of the objects in the database\n", "subsections": [] }, "SYNOPSIS": { "content": "git fsck [--tags] [--root] [--unreachable] [--cache] [--no-reflogs]\n[--[no-]full] [--strict] [--verbose] [--lost-found]\n[--[no-]dangling] [--[no-]progress] [--connectivity-only]\n[--[no-]name-objects] [*]\n\n", "subsections": [] }, "DESCRIPTION": { "content": "Verifies the connectivity and validity of the objects in the database.\n", "subsections": [] }, "OPTIONS": { "content": "\nAn object to treat as the head of an unreachability trace.\n\nIf no objects are given, git fsck defaults to using the index file, all SHA-1 references\nin refs namespace, and all reflogs (unless --no-reflogs is given) as heads.\n", "subsections": [ { "name": "--unreachable", "content": "Print out objects that exist but that aren’t reachable from any of the reference nodes.\n\n--[no-]dangling\nPrint objects that exist but that are never directly used (default). --no-dangling can\nbe used to omit this information from the output.\n", "long": "--unreachable" }, { "name": "--root", "content": "Report root nodes.\n", "long": "--root" }, { "name": "--tags", "content": "Report tags.\n", "long": "--tags" }, { "name": "--cache", "content": "Consider any object recorded in the index also as a head node for an unreachability\ntrace.\n", "long": "--cache" }, { "name": "--no-reflogs", "content": "Do not consider commits that are referenced only by an entry in a reflog to be reachable.\nThis option is meant only to search for commits that used to be in a ref, but now aren’t,\nbut are still in that corresponding reflog.\n", "long": "--no-reflogs" }, { "name": "--full", "content": "Check not just objects in GITOBJECTDIRECTORY ($GITDIR/objects), but also the ones\nfound in alternate object pools listed in GITALTERNATEOBJECTDIRECTORIES or\n$GITDIR/objects/info/alternates, and in packed Git archives found in\n$GITDIR/objects/pack and corresponding pack subdirectories in alternate object pools.\nThis is now default; you can turn it off with --no-full.\n", "long": "--full" }, { "name": "--connectivity-only", "content": "Check only the connectivity of reachable objects, making sure that any objects referenced\nby a reachable tag, commit, or tree is present. This speeds up the operation by avoiding\nreading blobs entirely (though it does still check that referenced blobs exist). This\nwill detect corruption in commits and trees, but not do any semantic checks (e.g., for\nformat errors). Corruption in blob objects will not be detected at all.\n\nUnreachable tags, commits, and trees will also be accessed to find the tips of dangling\nsegments of history. Use --no-dangling if you don’t care about this output and want to\nspeed it up further.\n", "long": "--connectivity-only" }, { "name": "--strict", "content": "Enable more strict checking, namely to catch a file mode recorded with g+w bit set, which\nwas created by older versions of Git. Existing repositories, including the Linux kernel,\nGit itself, and sparse repository have old objects that triggers this check, but it is\nrecommended to check new projects with this flag.\n", "long": "--strict" }, { "name": "--verbose", "content": "Be chatty.\n", "long": "--verbose" }, { "name": "--lost-found", "content": "Write dangling objects into .git/lost-found/commit/ or .git/lost-found/other/, depending\non type. If the object is a blob, the contents are written into the file, rather than its\nobject name.\n", "long": "--lost-found" }, { "name": "--name-objects", "content": "When displaying names of reachable objects, in addition to the SHA-1 also display a name\nthat describes how they are reachable, compatible with git-rev-parse(1), e.g.\nHEAD@{1234567890}~25^2:src/.\n\n--[no-]progress\nProgress status is reported on the standard error stream by default when it is attached\nto a terminal, unless --no-progress or --verbose is specified. --progress forces progress\nstatus even if the standard error stream is not directed to a terminal.\n", "long": "--name-objects" } ] }, "CONFIGURATION": { "content": "fsck.\nDuring fsck git may find issues with legacy data which wouldn’t be generated by current\nversions of git, and which wouldn’t be sent over the wire if transfer.fsckObjects was\nset. This feature is intended to support working with legacy repositories containing such\ndata.\n\nSetting fsck. will be picked up by git-fsck(1), but to accept pushes of such data\nset receive.fsck. instead, or to clone or fetch it set fetch.fsck..\n\nThe rest of the documentation discusses fsck.* for brevity, but the same applies for the\ncorresponding receive.fsck.* and fetch..*. variables.\n\nUnlike variables like color.ui and core.editor the receive.fsck. and\nfetch.fsck. variables will not fall back on the fsck. configuration if\nthey aren’t set. To uniformly configure the same fsck settings in different circumstances\nall three of them they must all set to the same values.\n\nWhen fsck. is set, errors can be switched to warnings and vice versa by\nconfiguring the fsck. setting where the is the fsck message ID and the\nvalue is one of error, warn or ignore. For convenience, fsck prefixes the error/warning\nwith the message ID, e.g. \"missingEmail: invalid author/committer line - missing email\"\nmeans that setting fsck.missingEmail = ignore will hide that issue.\n\nIn general, it is better to enumerate existing objects with problems with fsck.skipList,\ninstead of listing the kind of breakages these problematic objects share to be ignored,\nas doing the latter will allow new instances of the same breakages go unnoticed.\n\nSetting an unknown fsck. value will cause fsck to die, but doing the same for\nreceive.fsck. and fetch.fsck. will only cause git to warn.\n\nfsck.skipList\nThe path to a list of object names (i.e. one unabbreviated SHA-1 per line) that are known\nto be broken in a non-fatal way and should be ignored. On versions of Git 2.20 and later\ncomments (#), empty lines, and any leading and trailing whitespace is ignored. Everything\nbut a SHA-1 per line will error out on older versions.\n\nThis feature is useful when an established project should be accepted despite early\ncommits containing errors that can be safely ignored such as invalid committer email\naddresses. Note: corrupt objects cannot be skipped with this setting.\n\nLike fsck. this variable has corresponding receive.fsck.skipList and\nfetch.fsck.skipList variants.\n\nUnlike variables like color.ui and core.editor the receive.fsck.skipList and\nfetch.fsck.skipList variables will not fall back on the fsck.skipList configuration if\nthey aren’t set. To uniformly configure the same fsck settings in different circumstances\nall three of them they must all set to the same values.\n\nOlder versions of Git (before 2.20) documented that the object names list should be\nsorted. This was never a requirement, the object names could appear in any order, but\nwhen reading the list we tracked whether the list was sorted for the purposes of an\ninternal binary search implementation, which could save itself some work with an already\nsorted list. Unless you had a humongous list there was no reason to go out of your way to\npre-sort the list. After Git version 2.20 a hash implementation is used instead, so\nthere’s now no reason to pre-sort the list.\n", "subsections": [] }, "DISCUSSION": { "content": "git-fsck tests SHA-1 and general object sanity, and it does full tracking of the resulting\nreachability and everything else. It prints out any corruption it finds (missing or bad\nobjects), and if you use the --unreachable flag it will also print out objects that exist but\nthat aren’t reachable from any of the specified head nodes (or the default set, as mentioned\nabove).\n\nAny corrupt objects you will have to find in backups or other archives (i.e., you can just\nremove them and do an rsync with some other site in the hopes that somebody else has the\nobject you have corrupted).\n\nIf core.commitGraph is true, the commit-graph file will also be inspected using git\ncommit-graph verify. See git-commit-graph(1).\n", "subsections": [] }, "EXTRACTED DIAGNOSTICS": { "content": "unreachable \nThe object , isn’t actually referred to directly or indirectly in any of\nthe trees or commits seen. This can mean that there’s another root node that you’re not\nspecifying or that the tree is corrupt. If you haven’t missed a root node then you might\nas well delete unreachable nodes since they can’t be used.\n\nmissing \nThe object , is referred to but isn’t present in the database.\n\ndangling \nThe object , is present in the database but never directly used. A\ndangling commit could be a root node.\n\nhash mismatch \nThe database has an object whose hash doesn’t match the object database value. This\nindicates a serious data integrity problem.\n", "subsections": [] }, "ENVIRONMENT VARIABLES": { "content": "GITOBJECTDIRECTORY\nused to specify the object database root (usually $GITDIR/objects)\n\nGITINDEXFILE\nused to specify the index file of the index\n\nGITALTERNATEOBJECTDIRECTORIES\nused to specify additional object database roots (usually unset)\n", "subsections": [] }, "GIT": { "content": "Part of the git(1) suite\n\n\n\nGit 2.34.1 02/26/2026 GIT-FSCK(1)", "subsections": [] } }, "summary": "git-fsck - Verifies the connectivity and validity of the objects in the database", "flags": [ { "flag": "", "long": "--unreachable", "arg": null, "description": "Print out objects that exist but that aren’t reachable from any of the reference nodes. --[no-]dangling Print objects that exist but that are never directly used (default). --no-dangling can be used to omit this information from the output." }, { "flag": "", "long": "--root", "arg": null, "description": "Report root nodes." }, { "flag": "", "long": "--tags", "arg": null, "description": "Report tags." }, { "flag": "", "long": "--cache", "arg": null, "description": "Consider any object recorded in the index also as a head node for an unreachability trace." }, { "flag": "", "long": "--no-reflogs", "arg": null, "description": "Do not consider commits that are referenced only by an entry in a reflog to be reachable. This option is meant only to search for commits that used to be in a ref, but now aren’t, but are still in that corresponding reflog." }, { "flag": "", "long": "--full", "arg": null, "description": "Check not just objects in GITOBJECTDIRECTORY ($GITDIR/objects), but also the ones found in alternate object pools listed in GITALTERNATEOBJECTDIRECTORIES or $GITDIR/objects/info/alternates, and in packed Git archives found in $GITDIR/objects/pack and corresponding pack subdirectories in alternate object pools. This is now default; you can turn it off with --no-full." }, { "flag": "", "long": "--connectivity-only", "arg": null, "description": "Check only the connectivity of reachable objects, making sure that any objects referenced by a reachable tag, commit, or tree is present. This speeds up the operation by avoiding reading blobs entirely (though it does still check that referenced blobs exist). This will detect corruption in commits and trees, but not do any semantic checks (e.g., for format errors). Corruption in blob objects will not be detected at all. Unreachable tags, commits, and trees will also be accessed to find the tips of dangling segments of history. Use --no-dangling if you don’t care about this output and want to speed it up further." }, { "flag": "", "long": "--strict", "arg": null, "description": "Enable more strict checking, namely to catch a file mode recorded with g+w bit set, which was created by older versions of Git. Existing repositories, including the Linux kernel, Git itself, and sparse repository have old objects that triggers this check, but it is recommended to check new projects with this flag." }, { "flag": "", "long": "--verbose", "arg": null, "description": "Be chatty." }, { "flag": "", "long": "--lost-found", "arg": null, "description": "Write dangling objects into .git/lost-found/commit/ or .git/lost-found/other/, depending on type. If the object is a blob, the contents are written into the file, rather than its object name." }, { "flag": "", "long": "--name-objects", "arg": null, "description": "When displaying names of reachable objects, in addition to the SHA-1 also display a name that describes how they are reachable, compatible with git-rev-parse(1), e.g. HEAD@{1234567890}~25^2:src/. --[no-]progress Progress status is reported on the standard error stream by default when it is attached to a terminal, unless --no-progress or --verbose is specified. --progress forces progress status even if the standard error stream is not directed to a terminal." } ], "examples": [], "see_also": [] }