| blob | dade10e3a0682cb133033e139d73b59171029c00 |
1 '\" t
2 .\" Title: git-fsck
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
5 .\" Date: 2024-02-14
6 .\" Manual: Git Manual
7 .\" Source: Git 2.44.0.rc1.15.g4fc51f00ef
8 .\" Language: English
9 .\"
10 .TH "GIT\-FSCK" "1" "2024\-02\-14" "Git 2\&.44\&.0\&.rc1\&.15\&.g4" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18 .ie \n(.g .ds Aq \(aq
19 .el .ds Aq '
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
24 .nh
25 .\" disable justification (adjust text to left margin only)
26 .ad l
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
30 .SH "NAME"
31 git-fsck \- Verifies the connectivity and validity of the objects in the database
32 .SH "SYNOPSIS"
33 .sp
34 .nf
35 \fIgit fsck\fR [\-\-tags] [\-\-root] [\-\-unreachable] [\-\-cache] [\-\-no\-reflogs]
36 [\-\-[no\-]full] [\-\-strict] [\-\-verbose] [\-\-lost\-found]
37 [\-\-[no\-]dangling] [\-\-[no\-]progress] [\-\-connectivity\-only]
38 [\-\-[no\-]name\-objects] [<object>\&...]
39 .fi
40 .sp
41 .SH "DESCRIPTION"
42 .sp
43 Verifies the connectivity and validity of the objects in the database\&.
44 .SH "OPTIONS"
45 .PP
46 <object>
47 .RS 4
48 An object to treat as the head of an unreachability trace\&.
49 .sp
50 If no objects are given,
51 \fIgit fsck\fR
52 defaults to using the index file, all SHA\-1 references in the
53 \fBrefs\fR
54 namespace, and all reflogs (unless \-\-no\-reflogs is given) as heads\&.
55 .RE
56 .PP
57 \-\-unreachable
58 .RS 4
59 Print out objects that exist but that aren\(cqt reachable from any of the reference nodes\&.
60 .RE
61 .PP
62 \-\-[no\-]dangling
63 .RS 4
64 Print objects that exist but that are never
65 \fIdirectly\fR
66 used (default)\&.
67 \fB\-\-no\-dangling\fR
68 can be used to omit this information from the output\&.
69 .RE
70 .PP
71 \-\-root
72 .RS 4
73 Report root nodes\&.
74 .RE
75 .PP
76 \-\-tags
77 .RS 4
78 Report tags\&.
79 .RE
80 .PP
81 \-\-cache
82 .RS 4
83 Consider any object recorded in the index also as a head node for an unreachability trace\&.
84 .RE
85 .PP
86 \-\-no\-reflogs
87 .RS 4
88 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\(cqt, but are still in that corresponding reflog\&.
89 .RE
90 .PP
91 \-\-full
92 .RS 4
93 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\&.
94 .RE
95 .PP
96 \-\-connectivity\-only
97 .RS 4
98 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\&.
99 .sp
100 Unreachable tags, commits, and trees will also be accessed to find the tips of dangling segments of history\&. Use
101 \fB\-\-no\-dangling\fR
102 if you don\(cqt care about this output and want to speed it up further\&.
103 .RE
104 .PP
105 \-\-strict
106 .RS 4
107 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\&.
108 .RE
109 .PP
110 \-\-verbose
111 .RS 4
112 Be chatty\&.
113 .RE
114 .PP
115 \-\-lost\-found
116 .RS 4
117 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\&.
118 .RE
119 .PP
120 \-\-name\-objects
121 .RS 4
122 When displaying names of reachable objects, in addition to the SHA\-1 also display a name that describes
123 \fBhow\fR
124 they are reachable, compatible with
125 \fBgit-rev-parse\fR(1), e\&.g\&.
126 \fBHEAD@{1234567890}~25^2:src/\fR\&.
127 .RE
128 .PP
129 \-\-[no\-]progress
130 .RS 4
131 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\&.
132 .RE
133 .SH "CONFIGURATION"
134 .sp
135 Everything below this line in this section is selectively included from the \fBgit-config\fR(1) documentation\&. The content is the same as what\(cqs found there:
136 .PP
137 fsck\&.<msg\-id>
138 .RS 4
139 During fsck git may find issues with legacy data which wouldn\(cqt be generated by current versions of git, and which wouldn\(cqt be sent over the wire if
140 \fBtransfer\&.fsckObjects\fR
141 was set\&. This feature is intended to support working with legacy repositories containing such data\&.
142 .sp
143 Setting
144 \fBfsck\&.<msg\-id>\fR
145 will be picked up by
146 \fBgit-fsck\fR(1), but to accept pushes of such data set
147 \fBreceive\&.fsck\&.<msg\-id>\fR
148 instead, or to clone or fetch it set
149 \fBfetch\&.fsck\&.<msg\-id>\fR\&.
150 .sp
151 The rest of the documentation discusses
152 \fBfsck\&.*\fR
153 for brevity, but the same applies for the corresponding
154 \fBreceive\&.fsck\&.*\fR
155 and
156 \fBfetch\&.fsck\&.*\fR\&. variables\&.
157 .sp
158 Unlike variables like
159 \fBcolor\&.ui\fR
160 and
161 \fBcore\&.editor\fR, the
162 \fBreceive\&.fsck\&.<msg\-id>\fR
163 and
164 \fBfetch\&.fsck\&.<msg\-id>\fR
165 variables will not fall back on the
166 \fBfsck\&.<msg\-id>\fR
167 configuration if they aren\(cqt set\&. To uniformly configure the same fsck settings in different circumstances, all three of them must be set to the same values\&.
168 .sp
169 When
170 \fBfsck\&.<msg\-id>\fR
171 is set, errors can be switched to warnings and vice versa by configuring the
172 \fBfsck\&.<msg\-id>\fR
173 setting where the
174 \fB<msg\-id>\fR
175 is the fsck message ID and the value is one of
176 \fBerror\fR,
177 \fBwarn\fR
178 or
179 \fBignore\fR\&. For convenience, fsck prefixes the error/warning with the message ID, e\&.g\&. "missingEmail: invalid author/committer line \- missing email" means that setting
180 \fBfsck\&.missingEmail = ignore\fR
181 will hide that issue\&.
182 .sp
183 In general, it is better to enumerate existing objects with problems with
184 \fBfsck\&.skipList\fR, 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\&.
185 .sp
186 Setting an unknown
187 \fBfsck\&.<msg\-id>\fR
188 value will cause fsck to die, but doing the same for
189 \fBreceive\&.fsck\&.<msg\-id>\fR
190 and
191 \fBfetch\&.fsck\&.<msg\-id>\fR
192 will only cause git to warn\&.
193 .sp
194 See the
195 \fBFsck Messages\fR
196 section of
197 \fBgit-fsck\fR(1)
198 for supported values of
199 \fB<msg\-id>\fR\&.
200 .RE
201 .PP
202 fsck\&.skipList
203 .RS 4
204 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 (\fI#\fR), empty lines, and any leading and trailing whitespace are ignored\&. Everything but a SHA\-1 per line will error out on older versions\&.
205 .sp
206 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\&.
207 .sp
208 Like
209 \fBfsck\&.<msg\-id>\fR
210 this variable has corresponding
211 \fBreceive\&.fsck\&.skipList\fR
212 and
213 \fBfetch\&.fsck\&.skipList\fR
214 variants\&.
215 .sp
216 Unlike variables like
217 \fBcolor\&.ui\fR
218 and
219 \fBcore\&.editor\fR
220 the
221 \fBreceive\&.fsck\&.skipList\fR
222 and
223 \fBfetch\&.fsck\&.skipList\fR
224 variables will not fall back on the
225 \fBfsck\&.skipList\fR
226 configuration if they aren\(cqt set\&. To uniformly configure the same fsck settings in different circumstances, all three of them must be set to the same values\&.
227 .sp
228 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\(cqs now no reason to pre\-sort the list\&.
229 .RE
230 .SH "DISCUSSION"
231 .sp
232 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 \fB\-\-unreachable\fR flag it will also print out objects that exist but that aren\(cqt reachable from any of the specified head nodes (or the default set, as mentioned above)\&.
233 .sp
234 Any corrupt objects you will have to find in backups or other archives (i\&.e\&., you can just remove them and do an \fIrsync\fR with some other site in the hopes that somebody else has the object you have corrupted)\&.
235 .sp
236 If core\&.commitGraph is true, the commit\-graph file will also be inspected using \fIgit commit\-graph verify\fR\&. See \fBgit-commit-graph\fR(1)\&.
237 .SH "EXTRACTED DIAGNOSTICS"
238 .PP
239 unreachable <type> <object>
240 .RS 4
241 The <type> object <object>, isn\(cqt actually referred to directly or indirectly in any of the trees or commits seen\&. This can mean that there\(cqs another root node that you\(cqre not specifying or that the tree is corrupt\&. If you haven\(cqt missed a root node then you might as well delete unreachable nodes since they can\(cqt be used\&.
242 .RE
243 .PP
244 missing <type> <object>
245 .RS 4
246 The <type> object <object>, is referred to but isn\(cqt present in the database\&.
247 .RE
248 .PP
249 dangling <type> <object>
250 .RS 4
251 The <type> object <object>, is present in the database but never
252 \fIdirectly\fR
253 used\&. A dangling commit could be a root node\&.
254 .RE
255 .PP
256 hash mismatch <object>
257 .RS 4
258 The database has an object whose hash doesn\(cqt match the object database value\&. This indicates a serious data integrity problem\&.
259 .RE
260 .SH "FSCK MESSAGES"
261 .sp
262 The following lists the types of errors \fBgit fsck\fR 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 \fBfsck\&.<msg\-id>\fR configuration variable\&.
263 .PP
264 \fBbadDate\fR
265 .RS 4
266 (ERROR) Invalid date format in an author/committer line\&.
267 .RE
268 .PP
269 \fBbadDateOverflow\fR
270 .RS 4
271 (ERROR) Invalid date value in an author/committer line\&.
272 .RE
273 .PP
274 \fBbadEmail\fR
275 .RS 4
276 (ERROR) Invalid email format in an author/committer line\&.
277 .RE
278 .PP
279 \fBbadFilemode\fR
280 .RS 4
281 (INFO) A tree contains a bad filemode entry\&.
282 .RE
283 .PP
284 \fBbadName\fR
285 .RS 4
286 (ERROR) An author/committer name is empty\&.
287 .RE
288 .PP
289 \fBbadObjectSha1\fR
290 .RS 4
291 (ERROR) An object has a bad sha1\&.
292 .RE
293 .PP
294 \fBbadParentSha1\fR
295 .RS 4
296 (ERROR) A commit object has a bad parent sha1\&.
297 .RE
298 .PP
299 \fBbadTagName\fR
300 .RS 4
301 (INFO) A tag has an invalid format\&.
302 .RE
303 .PP
304 \fBbadTimezone\fR
305 .RS 4
306 (ERROR) Found an invalid time zone in an author/committer line\&.
307 .RE
308 .PP
309 \fBbadTree\fR
310 .RS 4
311 (ERROR) A tree cannot be parsed\&.
312 .RE
313 .PP
314 \fBbadTreeSha1\fR
315 .RS 4
316 (ERROR) A tree has an invalid format\&.
317 .RE
318 .PP
319 \fBbadType\fR
320 .RS 4
321 (ERROR) Found an invalid object type\&.
322 .RE
323 .PP
324 \fBduplicateEntries\fR
325 .RS 4
326 (ERROR) A tree contains duplicate file entries\&.
327 .RE
328 .PP
329 \fBemptyName\fR
330 .RS 4
331 (WARN) A path contains an empty name\&.
332 .RE
333 .PP
334 \fBextraHeaderEntry\fR
335 .RS 4
336 (IGNORE) Extra headers found after
337 \fBtagger\fR\&.
338 .RE
339 .PP
340 \fBfullPathname\fR
341 .RS 4
342 (WARN) A path contains the full path starting with "/"\&.
343 .RE
344 .PP
345 \fBgitattributesBlob\fR
346 .RS 4
347 (ERROR) A non\-blob found at
348 \fB\&.gitattributes\fR\&.
349 .RE
350 .PP
351 \fBgitattributesLarge\fR
352 .RS 4
353 (ERROR) The
354 \fB\&.gitattributes\fR
355 blob is too large\&.
356 .RE
357 .PP
358 \fBgitattributesLineLength\fR
359 .RS 4
360 (ERROR) The
361 \fB\&.gitattributes\fR
362 blob contains too long lines\&.
363 .RE
364 .PP
365 \fBgitattributesMissing\fR
366 .RS 4
367 (ERROR) Unable to read
368 \fB\&.gitattributes\fR
369 blob\&.
370 .RE
371 .PP
372 \fBgitattributesSymlink\fR
373 .RS 4
374 (INFO)
375 \fB\&.gitattributes\fR
376 is a symlink\&.
377 .RE
378 .PP
379 \fBgitignoreSymlink\fR
380 .RS 4
381 (INFO)
382 \fB\&.gitignore\fR
383 is a symlink\&.
384 .RE
385 .PP
386 \fBgitmodulesBlob\fR
387 .RS 4
388 (ERROR) A non\-blob found at
389 \fB\&.gitmodules\fR\&.
390 .RE
391 .PP
392 \fBgitmodulesLarge\fR
393 .RS 4
394 (ERROR) The
395 \fB\&.gitmodules\fR
396 file is too large to parse\&.
397 .RE
398 .PP
399 \fBgitmodulesMissing\fR
400 .RS 4
401 (ERROR) Unable to read
402 \fB\&.gitmodules\fR
403 blob\&.
404 .RE
405 .PP
406 \fBgitmodulesName\fR
407 .RS 4
408 (ERROR) A submodule name is invalid\&.
409 .RE
410 .PP
411 \fBgitmodulesParse\fR
412 .RS 4
413 (INFO) Could not parse
414 \fB\&.gitmodules\fR
415 blob\&.
416 .RE
417 .sp
418 \fBgitmodulesLarge\fR; (ERROR) \fB\&.gitmodules\fR blob is too large to parse\&.
419 .PP
420 \fBgitmodulesPath\fR
421 .RS 4
422 (ERROR)
423 \fB\&.gitmodules\fR
424 path is invalid\&.
425 .RE
426 .PP
427 \fBgitmodulesSymlink\fR
428 .RS 4
429 (ERROR)
430 \fB\&.gitmodules\fR
431 is a symlink\&.
432 .RE
433 .PP
434 \fBgitmodulesUpdate\fR
435 .RS 4
436 (ERROR) Found an invalid submodule update setting\&.
437 .RE
438 .PP
439 \fBgitmodulesUrl\fR
440 .RS 4
441 (ERROR) Found an invalid submodule url\&.
442 .RE
443 .PP
444 \fBhasDot\fR
445 .RS 4
446 (WARN) A tree contains an entry named
447 \fB\&.\fR\&.
448 .RE
449 .PP
450 \fBhasDotdot\fR
451 .RS 4
452 (WARN) A tree contains an entry named
453 \fB\&.\&.\fR\&.
454 .RE
455 .PP
456 \fBhasDotgit\fR
457 .RS 4
458 (WARN) A tree contains an entry named
459 \fB\&.git\fR\&.
460 .RE
461 .PP
462 \fBlargePathname\fR
463 .RS 4
464 (WARN) A tree contains an entry with a very long path name\&. If the value of
465 \fBfsck\&.largePathname\fR
466 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\&.
467 .RE
468 .PP
469 \fBmailmapSymlink\fR
470 .RS 4
471 (INFO)
472 \fB\&.mailmap\fR
473 is a symlink\&.
474 .RE
475 .PP
476 \fBmissingAuthor\fR
477 .RS 4
478 (ERROR) Author is missing\&.
479 .RE
480 .PP
481 \fBmissingCommitter\fR
482 .RS 4
483 (ERROR) Committer is missing\&.
484 .RE
485 .PP
486 \fBmissingEmail\fR
487 .RS 4
488 (ERROR) Email is missing in an author/committer line\&.
489 .RE
490 .PP
491 \fBmissingNameBeforeEmail\fR
492 .RS 4
493 (ERROR) Missing name before an email in an author/committer line\&.
494 .RE
495 .PP
496 \fBmissingObject\fR
497 .RS 4
498 (ERROR) Missing
499 \fBobject\fR
500 line in tag object\&.
501 .RE
502 .PP
503 \fBmissingSpaceBeforeDate\fR
504 .RS 4
505 (ERROR) Missing space before date in an author/committer line\&.
506 .RE
507 .PP
508 \fBmissingSpaceBeforeEmail\fR
509 .RS 4
510 (ERROR) Missing space before the email in an author/committer line\&.
511 .RE
512 .PP
513 \fBmissingTag\fR
514 .RS 4
515 (ERROR) Unexpected end after
516 \fBtype\fR
517 line in a tag object\&.
518 .RE
519 .PP
520 \fBmissingTagEntry\fR
521 .RS 4
522 (ERROR) Missing
523 \fBtag\fR
524 line in a tag object\&.
525 .RE
526 .PP
527 \fBmissingTaggerEntry\fR
528 .RS 4
529 (INFO) Missing
530 \fBtagger\fR
531 line in a tag object\&.
532 .RE
533 .PP
534 \fBmissingTree\fR
535 .RS 4
536 (ERROR) Missing
537 \fBtree\fR
538 line in a commit object\&.
539 .RE
540 .PP
541 \fBmissingType\fR
542 .RS 4
543 (ERROR) Invalid type value on the
544 \fBtype\fR
545 line in a tag object\&.
546 .RE
547 .PP
548 \fBmissingTypeEntry\fR
549 .RS 4
550 (ERROR) Missing
551 \fBtype\fR
552 line in a tag object\&.
553 .RE
554 .PP
555 \fBmultipleAuthors\fR
556 .RS 4
557 (ERROR) Multiple author lines found in a commit\&.
558 .RE
559 .PP
560 \fBnulInCommit\fR
561 .RS 4
562 (WARN) Found a NUL byte in the commit object body\&.
563 .RE
564 .PP
565 \fBnulInHeader\fR
566 .RS 4
567 (FATAL) NUL byte exists in the object header\&.
568 .RE
569 .PP
570 \fBnullSha1\fR
571 .RS 4
572 (WARN) Tree contains entries pointing to a null sha1\&.
573 .RE
574 .PP
575 \fBtreeNotSorted\fR
576 .RS 4
577 (ERROR) A tree is not properly sorted\&.
578 .RE
579 .PP
580 \fBunknownType\fR
581 .RS 4
582 (ERROR) Found an unknown object type\&.
583 .RE
584 .PP
585 \fBunterminatedHeader\fR
586 .RS 4
587 (FATAL) Missing end\-of\-line in the object header\&.
588 .RE
589 .PP
590 \fBzeroPaddedDate\fR
591 .RS 4
592 (ERROR) Found a zero padded date in an author/committer line\&.
593 .RE
594 .PP
595 \fBzeroPaddedFilemode\fR
596 .RS 4
597 (WARN) Found a zero padded filemode in a tree\&.
598 .RE
599 .SH "ENVIRONMENT VARIABLES"
600 .PP
601 GIT_OBJECT_DIRECTORY
602 .RS 4
603 used to specify the object database root (usually $GIT_DIR/objects)
604 .RE
605 .PP
606 GIT_INDEX_FILE
607 .RS 4
608 used to specify the index file of the index
609 .RE
610 .PP
611 GIT_ALTERNATE_OBJECT_DIRECTORIES
612 .RS 4
613 used to specify additional object database roots (usually unset)
614 .RE
615 .SH "GIT"
616 .sp
617 Part of the \fBgit\fR(1) suite