git-fsck - Verifies the connectivity and validity of the objects in the


   git fsck [--tags] [--root] [--unreachable] [--cache] [--no-reflogs]
            [--[no-]full] [--strict] [--verbose] [--lost-found]
            [--[no-]dangling] [--[no-]progress] [--connectivity-only]
            [--[no-]name-objects] [<object>*]


   Verifies the connectivity and validity of the objects in the database.


       An object to treat as the head of an unreachability trace.

       If no objects are given, git fsck defaults to using the index file,
       all SHA-1 references in refs namespace, and all reflogs (unless
       --no-reflogs is given) as heads.

       Print out objects that exist but that aren't reachable from any of
       the reference nodes.

       Print objects that exist but that are never directly used
       (default).  --no-dangling can be used to omit this information from
       the output.

       Report root nodes.

       Report tags.

       Consider any object recorded in the index also as a head node for
       an unreachability trace.

       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.

       Check not just objects in GIT_OBJECT_DIRECTORY ($GIT_DIR/objects),
       but also the ones found in alternate object pools listed in
       $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.

       Check only the connectivity of tags, commits and tree objects. By
       avoiding to unpack blobs, this speeds up the operation, at the
       expense of missing corrupt objects or other problematic issues.

       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.

       Be chatty.

       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

       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.

       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.


   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 --unreachable 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).

   Any corrupt objects you will have to find in backups or other archives
   (i.e., you can just remove them and do an rsync with some other site in
   the hopes that somebody else has the object you have corrupted).


   expect dangling commits - potential heads - due to lack of head
       You haven't specified any nodes as heads so it won't be possible to
       differentiate between un-parented commits and root nodes.

   missing sha1 directory <dir>
       The directory holding the sha1 objects is missing.

   unreachable <type> <object>
       The <type> object <object>, 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.

   missing <type> <object>
       The <type> object <object>, is referred to but isn't present in the

   dangling <type> <object>
       The <type> object <object>, is present in the database but never
       directly used. A dangling commit could be a root node.

   sha1 mismatch <object>
       The database has an object who's sha1 doesn't match the database
       value. This indicates a serious data integrity problem.


       used to specify the object database root (usually $GIT_DIR/objects)

       used to specify the index file of the index

       used to specify additional object database roots (usually unset)


   Part of the git(1) suite

More Linux Commands

xdrrec_create(3) - library routines for external data repres
These routines allow C programmers to describe arbitrary data structures in a machine-independent fashion. Data for remote procedure calls are transmitted using

xzdec(1) - Small .xz and .lzma decompressors (Man Page).....
xzdec is a liblzma-based decompression-only tool for .xz (and only .xz) files. xzdec is intended to work as a drop-in replacement for xz(1) in the most common s

regcomp(3) - POSIX regex functions - Linux manual page......
POSIX regex compiling regcomp() is used to compile a regular expression into a form that is suitable for subsequent regexec() searches. regcomp() is supplied wi

set_field_buffer(3form) - field buffer control (Man Page)...
The function set_field_buffer sets the numbered buffer of the given field to contain a given string: * Buffer 0 is the displayed value of the field. * Other num

gnutls_x509_crt_set_subject_alt_name(3) - API function......
gnutls_x509_crt_set_subject_alt_name.3 - This function will set the subject alternative name certificate extension. It can set the following types: RETURNS On s

snmpbulkwalk(1) - retrieve a subtree of management values us
snmpbulkwalk is an SNMP application that uses SNMP GETBULK requests to query a network entity efficiently for a tree of information. An object identifier (OID)

killpg(2) - send signal to a process group - Linux man page
killpg() sends the signal sig to the process group pgrp. See signal(7) for a list of signals. If pgrp is 0, killpg() sends the signal to the calling processs pr

hciattach(8) - attach serial devices via UART HCI to BlueZ s
hciattach.8 - Hciattach is used to attach a serial UART to the Bluetooth stack as HCI transport interface. OPTIONS -b Send break. -n Dont detach from controllin

XkbAllocClientMap(3) - Allocate and initialize an empty clie
Calling XkbGetMap should be sufficient for most applications to get client and server maps. As a result, most applications do not need to directly allocate clie

XGCValues(3) - create or free graphics contexts and graphics
The XCreateGC function creates a graphics context and returns a GC. The GC can be used with any destination drawable having the same root and depth as the speci

casinh(3) - complex arc sine hyperbolic - Linux manual page
The casinh() function calculates the complex arc hyperbolic sine of z. If y = casinh(z), then z = csinh(y). The imaginary part of y is chosen in the interval [-

glVertex3f(3gl) - specify a vertex - Linux manual page......
glVertex commands are used within glBegin/glEnd pairs to specify point, line, and polygon vertices. The current color, normal, and texture coordinates are assoc

We can't live, work or learn in freedom unless the software we use is free.