<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sect2 SYSTEM "../../../dtd/dblite.dtd">

<sect2 lang="en" id="git-fsck(1)">
    <title>git-fsck(1)</title>
    <date>2024-07-02</date>
<revhistory><revision><date>2024-07-02</date></revision></revhistory>
<indexterm>
<primary>git-fsck(1)</primary>
</indexterm>
<simplesect id="git-fsck(1)__name">
<title>NAME</title>
<simpara>git-fsck - Verifies the connectivity and validity of the objects in the database</simpara>
</simplesect>
<simplesect id="git-fsck(1)__synopsis">
<title>SYNOPSIS</title>
<blockquote>
<literallayout><emphasis>git fsck</emphasis> [--tags] [--root] [--unreachable] [--cache] [--no-reflogs]
         [--[no-]full] [--strict] [--verbose] [--lost-found]
         [--[no-]dangling] [--[no-]progress] [--connectivity-only]
         [--[no-]name-objects] [&lt;object&gt;&#8230;]</literallayout>
</blockquote>
</simplesect>
<simplesect id="git-fsck(1)__description">
<title>DESCRIPTION</title>
<simpara>Verifies the connectivity and validity of the objects in the database.</simpara>
</simplesect>
<simplesect id="git-fsck(1)__options">
<title>OPTIONS</title>
<variablelist>
<varlistentry>
<term>
&lt;object&gt;
</term>
<listitem>
<simpara>
        An object to treat as the head of an unreachability trace.
</simpara>
<simpara>If no objects are given, <emphasis>git fsck</emphasis> defaults to using the
index file, all SHA-1 references in the <emphasis>refs</emphasis> namespace, and all reflogs
(unless --no-reflogs is given) as heads.</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--unreachable
</term>
<listitem>
<simpara>
        Print out objects that exist but that aren't reachable from any
        of the reference nodes.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--[no-]dangling
</term>
<listitem>
<simpara>
        Print objects that exist but that are never <emphasis>directly</emphasis> used (default).
        <emphasis>--no-dangling</emphasis> can be used to omit this information from the output.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--root
</term>
<listitem>
<simpara>
        Report root nodes.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--tags
</term>
<listitem>
<simpara>
        Report tags.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--cache
</term>
<listitem>
<simpara>
        Consider any object recorded in the index also as a head node for
        an unreachability trace.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--no-reflogs
</term>
<listitem>
<simpara>
        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.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--full
</term>
<listitem>
<simpara>
        Check not just objects in GIT_OBJECT_DIRECTORY
        ($GIT_DIR/objects), but also the ones found in alternate
        object pools listed in GIT_ALTERNATE_OBJECT_DIRECTORIES
        or $GIT_DIR/objects/info/alternates,
        and in packed Git archives found in $GIT_DIR/objects/pack
        and corresponding pack subdirectories in alternate
        object pools.  This is now default; you can turn it off
        with --no-full.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--connectivity-only
</term>
<listitem>
<simpara>
        Check only the connectivity of reachable objects, making sure
        that any objects referenced by a reachable tag, commit, or tree
        are 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.
</simpara>
<simpara>Unreachable tags, commits, and trees will also be accessed to find the
tips of dangling segments of history. Use <emphasis>--no-dangling</emphasis> if you don't
care about this output and want to speed it up further.</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--strict
</term>
<listitem>
<simpara>
        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 trigger this check, but it is recommended
        to check new projects with this flag.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--verbose
</term>
<listitem>
<simpara>
        Be chatty.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--lost-found
</term>
<listitem>
<simpara>
        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.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--name-objects
</term>
<listitem>
<simpara>
        When displaying names of reachable objects, in addition to the
        SHA-1 also display a name that describes <emphasis role="strong">how</emphasis> they are reachable,
        compatible with <xref linkend="git-rev-parse(1)" />, e.g.
        <emphasis>HEAD@{1234567890}~25^2:src/</emphasis>.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
--[no-]progress
</term>
<listitem>
<simpara>
        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.
</simpara>
</listitem>
</varlistentry>
</variablelist>
</simplesect>
<simplesect id="git-fsck(1)__configuration">
<title>CONFIGURATION</title>
<simpara>Everything below this line in this section is selectively included
from the <xref linkend="git-config(1)" /> documentation. The content is the same
as what's found there:</simpara>
<variablelist>
<varlistentry>
<term>
fsck.&lt;msg-id&gt;
</term>
<listitem>
<simpara>
        During fsck git may find issues with legacy data which
        wouldn't be generated by current versions of git, and which
        wouldn't be sent over the wire if <emphasis>transfer.fsckObjects</emphasis> was
        set. This feature is intended to support working with legacy
        repositories containing such data.
</simpara>
<simpara>Setting <emphasis>fsck.&lt;msg-id&gt;</emphasis> will be picked up by <xref linkend="git-fsck(1)" />, but
to accept pushes of such data set <emphasis>receive.fsck.&lt;msg-id&gt;</emphasis> instead, or
to clone or fetch it set <emphasis>fetch.fsck.&lt;msg-id&gt;</emphasis>.</simpara>
<simpara>The rest of the documentation discusses <emphasis>fsck.*</emphasis> for brevity, but the
same applies for the corresponding <emphasis>receive.fsck.*</emphasis> and
<emphasis>fetch.fsck.*</emphasis>. variables.</simpara>
<simpara>Unlike variables like <emphasis>color.ui</emphasis> and <emphasis>core.editor</emphasis>, the
<emphasis>receive.fsck.&lt;msg-id&gt;</emphasis> and <emphasis>fetch.fsck.&lt;msg-id&gt;</emphasis> variables will not
fall back on the <emphasis>fsck.&lt;msg-id&gt;</emphasis> configuration if they aren't set. To
uniformly configure the same fsck settings in different circumstances,
all three of them must be set to the same values.</simpara>
<simpara>When <emphasis>fsck.&lt;msg-id&gt;</emphasis> is set, errors can be switched to warnings and
vice versa by configuring the <emphasis>fsck.&lt;msg-id&gt;</emphasis> setting where the
<emphasis>&lt;msg-id&gt;</emphasis> is the fsck message ID and the value is one of <emphasis>error</emphasis>,
<emphasis>warn</emphasis> or <emphasis>ignore</emphasis>. For convenience, fsck prefixes the error/warning
with the message ID, e.g. "missingEmail: invalid author/committer
line - missing email" means that setting <emphasis>fsck.missingEmail = ignore</emphasis>
will hide that issue.</simpara>
<simpara>In general, it is better to enumerate existing objects with problems
with <emphasis>fsck.skipList</emphasis>, instead of listing the kind of breakages these
problematic objects share to be ignored, as doing the latter will
allow new instances of the same breakages go unnoticed.</simpara>
<simpara>Setting an unknown <emphasis>fsck.&lt;msg-id&gt;</emphasis> value will cause fsck to die, but
doing the same for <emphasis>receive.fsck.&lt;msg-id&gt;</emphasis> and <emphasis>fetch.fsck.&lt;msg-id&gt;</emphasis>
will only cause git to warn.</simpara>
<simpara>See the <emphasis>Fsck Messages</emphasis> section of <xref linkend="git-fsck(1)" /> for supported
values of <emphasis>&lt;msg-id&gt;</emphasis>.</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
fsck.skipList
</term>
<listitem>
<simpara>
        The path to a list of object names (i.e. one unabbreviated SHA-1 per
        line) that are known to be broken in a non-fatal way and should
        be ignored. On versions of Git 2.20 and later, comments (<emphasis>#</emphasis>), empty
        lines, and any leading and trailing whitespace are ignored. Everything
        but a SHA-1 per line will error out on older versions.
</simpara>
<simpara>This feature is useful when an established project should be accepted
despite early commits containing errors that can be safely ignored,
such as invalid committer email addresses.  Note: corrupt objects
cannot be skipped with this setting.</simpara>
<simpara>Like <emphasis>fsck.&lt;msg-id&gt;</emphasis> this variable has corresponding
<emphasis>receive.fsck.skipList</emphasis> and <emphasis>fetch.fsck.skipList</emphasis> variants.</simpara>
<simpara>Unlike variables like <emphasis>color.ui</emphasis> and <emphasis>core.editor</emphasis> the
<emphasis>receive.fsck.skipList</emphasis> and <emphasis>fetch.fsck.skipList</emphasis> variables will not
fall back on the <emphasis>fsck.skipList</emphasis> configuration if they aren't set. To
uniformly configure the same fsck settings in different circumstances,
all three of them must be set to the same values.</simpara>
<simpara>Older versions of Git (before 2.20) documented that the object names
list should be sorted. This was never a requirement; the object names
could appear in any order, but when reading the list we tracked whether
the list was sorted for the purposes of an internal binary search
implementation, which could save itself some work with an already sorted
list. Unless you had a humongous list there was no reason to go out of
your way to pre-sort the list. After Git version 2.20 a hash implementation
is used instead, so there's now no reason to pre-sort the list.</simpara>
</listitem>
</varlistentry>
</variablelist>
</simplesect>
<simplesect id="git-fsck(1)__discussion">
<title>DISCUSSION</title>
<simpara>git-fsck tests SHA-1 and general object sanity, and it does full tracking
of the resulting reachability and everything else. It prints out any
corruption it finds (missing or bad objects), and if you use the
<emphasis>--unreachable</emphasis> flag it will also print out objects that exist but that
aren't reachable from any of the specified head nodes (or the default
set, as mentioned above).</simpara>
<simpara>Any corrupt objects you will have to find in backups or other archives
(i.e., you can just remove them and do an <emphasis>rsync</emphasis> with some other site in
the hopes that somebody else has the object you have corrupted).</simpara>
<simpara>If core.commitGraph is true, the commit-graph file will also be inspected
using <emphasis>git commit-graph verify</emphasis>. See <xref linkend="git-commit-graph(1)" />.</simpara>
</simplesect>
<simplesect id="git-fsck(1)__extracted_diagnostics">
<title>Extracted Diagnostics</title>
<variablelist>
<varlistentry>
<term>
unreachable &lt;type&gt; &lt;object&gt;
</term>
<listitem>
<simpara>
        The &lt;type&gt; object &lt;object&gt;, isn't actually referred to directly
        or indirectly in any of the trees or commits seen. This can
        mean that there's another root node that you're not specifying
        or that the tree is corrupt. If you haven't missed a root node
        then you might as well delete unreachable nodes since they
        can't be used.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
missing &lt;type&gt; &lt;object&gt;
</term>
<listitem>
<simpara>
        The &lt;type&gt; object &lt;object&gt;, is referred to but isn't present in
        the database.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
dangling &lt;type&gt; &lt;object&gt;
</term>
<listitem>
<simpara>
        The &lt;type&gt; object &lt;object&gt;, is present in the database but never
        <emphasis>directly</emphasis> used. A dangling commit could be a root node.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
hash mismatch &lt;object&gt;
</term>
<listitem>
<simpara>
        The database has an object whose hash doesn't match the
        object database value.
        This indicates a serious data integrity problem.
</simpara>
</listitem>
</varlistentry>
</variablelist>
</simplesect>
<simplesect id="git-fsck(1)__fsck_messages">
<title>FSCK MESSAGES</title>
<simpara>The following lists the types of errors <emphasis>git fsck</emphasis> detects and what
each error means, with their default severity.  The severity of the
error, other than those that are marked as "(FATAL)", can be tweaked
by setting the corresponding <emphasis>fsck.&lt;msg-id&gt;</emphasis> configuration variable.</simpara>
<variablelist>
<varlistentry>
<term>
<emphasis>badDate</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Invalid date format in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badDateOverflow</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Invalid date value in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badEmail</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Invalid email format in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badFilemode</emphasis>
</term>
<listitem>
<simpara>
        (INFO) A tree contains a bad filemode entry.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badName</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) An author/committer name is empty.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badObjectSha1</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) An object has a bad sha1.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badParentSha1</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) A commit object has a bad parent sha1.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badTagName</emphasis>
</term>
<listitem>
<simpara>
        (INFO) A tag has an invalid format.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badTimezone</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Found an invalid time zone in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badTree</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) A tree cannot be parsed.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badTreeSha1</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) A tree has an invalid format.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>badType</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Found an invalid object type.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>duplicateEntries</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) A tree contains duplicate file entries.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>emptyName</emphasis>
</term>
<listitem>
<simpara>
        (WARN) A path contains an empty name.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>extraHeaderEntry</emphasis>
</term>
<listitem>
<simpara>
        (IGNORE) Extra headers found after <emphasis>tagger</emphasis>.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>fullPathname</emphasis>
</term>
<listitem>
<simpara>
        (WARN) A path contains the full path starting with "/".
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitattributesBlob</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) A non-blob found at <emphasis>.gitattributes</emphasis>.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitattributesLarge</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) The <emphasis>.gitattributes</emphasis> blob is too large.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitattributesLineLength</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) The <emphasis>.gitattributes</emphasis> blob contains too long lines.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitattributesMissing</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Unable to read <emphasis>.gitattributes</emphasis> blob.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitattributesSymlink</emphasis>
</term>
<listitem>
<simpara>
        (INFO) <emphasis>.gitattributes</emphasis> is a symlink.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitignoreSymlink</emphasis>
</term>
<listitem>
<simpara>
        (INFO) <emphasis>.gitignore</emphasis> is a symlink.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitmodulesBlob</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) A non-blob found at <emphasis>.gitmodules</emphasis>.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitmodulesLarge</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) The <emphasis>.gitmodules</emphasis> file is too large to parse.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitmodulesMissing</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Unable to read <emphasis>.gitmodules</emphasis> blob.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitmodulesName</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) A submodule name is invalid.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitmodulesParse</emphasis>
</term>
<listitem>
<simpara>
        (INFO) Could not parse <emphasis>.gitmodules</emphasis> blob.
</simpara>
</listitem>
</varlistentry>
</variablelist>
<simpara><emphasis>gitmodulesLarge</emphasis>;
        (ERROR) <emphasis>.gitmodules</emphasis> blob is too large to parse.</simpara>
<variablelist>
<varlistentry>
<term>
<emphasis>gitmodulesPath</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) <emphasis>.gitmodules</emphasis> path is invalid.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitmodulesSymlink</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) <emphasis>.gitmodules</emphasis> is a symlink.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitmodulesUpdate</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Found an invalid submodule update setting.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>gitmodulesUrl</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Found an invalid submodule url.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>hasDot</emphasis>
</term>
<listitem>
<simpara>
        (WARN) A tree contains an entry named <emphasis>.</emphasis>.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>hasDotdot</emphasis>
</term>
<listitem>
<simpara>
        (WARN) A tree contains an entry named <emphasis>..</emphasis>.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>hasDotgit</emphasis>
</term>
<listitem>
<simpara>
        (WARN) A tree contains an entry named <emphasis>.git</emphasis>.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>largePathname</emphasis>
</term>
<listitem>
<simpara>
        (WARN) A tree contains an entry with a very long path name. If
        the value of <emphasis>fsck.largePathname</emphasis> contains a colon, that value
        is used as the maximum allowable length (e.g., "warn:10" would
        complain about any path component of 11 or more bytes). The
        default value is 4096.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>mailmapSymlink</emphasis>
</term>
<listitem>
<simpara>
        (INFO) <emphasis>.mailmap</emphasis> is a symlink.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingAuthor</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Author is missing.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingCommitter</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Committer is missing.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingEmail</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Email is missing in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingNameBeforeEmail</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Missing name before an email in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingObject</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Missing <emphasis>object</emphasis> line in tag object.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingSpaceBeforeDate</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Missing space before date in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingSpaceBeforeEmail</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Missing space before the email in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingTag</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Unexpected end after <emphasis>type</emphasis> line in a tag object.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingTagEntry</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Missing <emphasis>tag</emphasis> line in a tag object.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingTaggerEntry</emphasis>
</term>
<listitem>
<simpara>
        (INFO) Missing <emphasis>tagger</emphasis> line in a tag object.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingTree</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Missing <emphasis>tree</emphasis> line in a commit object.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingType</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Invalid type value on the <emphasis>type</emphasis> line in a tag object.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>missingTypeEntry</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Missing <emphasis>type</emphasis> line in a tag object.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>multipleAuthors</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Multiple author lines found in a commit.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>nulInCommit</emphasis>
</term>
<listitem>
<simpara>
        (WARN) Found a NUL byte in the commit object body.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>nulInHeader</emphasis>
</term>
<listitem>
<simpara>
        (FATAL) NUL byte exists in the object header.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>nullSha1</emphasis>
</term>
<listitem>
<simpara>
        (WARN) Tree contains entries pointing to a null sha1.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>treeNotSorted</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) A tree is not properly sorted.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>unknownType</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Found an unknown object type.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>unterminatedHeader</emphasis>
</term>
<listitem>
<simpara>
        (FATAL) Missing end-of-line in the object header.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>zeroPaddedDate</emphasis>
</term>
<listitem>
<simpara>
        (ERROR) Found a zero padded date in an author/committer line.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<emphasis>zeroPaddedFilemode</emphasis>
</term>
<listitem>
<simpara>
        (WARN) Found a zero padded filemode in a tree.
</simpara>
</listitem>
</varlistentry>
</variablelist>
</simplesect>
<simplesect id="git-fsck(1)__environment_variables">
<title>Environment Variables</title>
<variablelist>
<varlistentry>
<term>
GIT_OBJECT_DIRECTORY
</term>
<listitem>
<simpara>
        used to specify the object database root (usually $GIT_DIR/objects)
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
GIT_INDEX_FILE
</term>
<listitem>
<simpara>
        used to specify the index file of the index
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
GIT_ALTERNATE_OBJECT_DIRECTORIES
</term>
<listitem>
<simpara>
        used to specify additional object database roots (usually unset)
</simpara>
</listitem>
</varlistentry>
</variablelist>
</simplesect>
<simplesect id="git-fsck(1)__git">
<title>GIT</title>
<simpara>Part of the <xref linkend="git(1)" /> suite</simpara>
</simplesect>
</sect2>
