blob: d363c68cebcea297feaa0858eb9650a2853d9956 [file] [log] [blame]
bigbiff bigbiff9c754052013-01-09 09:09:08 -05001.TH DOSFSCK 8 "2010\-01\-31" "3.0.9" "check and repair MS\-DOS filesystems"
2
3.SH NAME
4\fBdosfsck\fR \- check and repair MS\-DOS filesystems
5
6.SH SYNOPSIS
7\fBdosfsck\fR|\fBfsck.msdos\fR|\fBfsck.vfat\fR [\-aAflnrtvVwy] [\-d \fIPATH\fR \-d\ \fI...\fR] [\-u\ \fIPATH\fR \-u \fI...\fR] \fIDEVICE\fR
8
9.SH DESCRIPTION
10\fBdosfsck\fR verifies the consistency of MS\-DOS filesystems and optionally tries to repair them.
11.PP
12The following filesystem problems can be corrected (in this order):
13.IP "*" 4
14FAT contains invalid cluster numbers. Cluster is changed to EOF.
15.IP "*" 4
16File's cluster chain contains a loop. The loop is broken.
17.IP "*" 4
18Bad clusters (read errors). The clusters are marked bad and they are removed from files owning them. This check is optional.
19.IP "*" 4
20Directories with a large number of bad entries (probably corrupt). The directory can be deleted.
21.IP "*" 4
22Files . and .. are non\-directories. They can be deleted or renamed.
23.IP "*" 4
24Directories . and .. in root directory. They are deleted.
25.IP "*" 4
26Bad filenames. They can be renamed.
27.IP "*" 4
28Duplicate directory entries. They can be deleted or renamed.
29.IP "*" 4
30Directories with non\-zero size field. Size is set to zero.
31.IP "*" 4
32Directory . does not point to parent directory. The start pointer is adjusted.
33.IP "*" 4
34Directory .. does not point to parent of parent directory. The start pointer is adjusted.
35.IP "*" 4
36Start cluster number of a file is invalid. The file is truncated.
37.IP "*" 4
38File contains bad or free clusters. The file is truncated.
39.IP "*" 4
40File's cluster chain is longer than indicated by the size fields. The file is truncated.
41.IP "*" 4
42Two or more files share the same cluster(s). All but one of the files are truncated. If the file being truncated is a directory file that has already been read, the filesystem check is restarted after truncation.
43.IP "*" 4
44File's cluster chain is shorter than indicated by the size fields. The file is truncated.
45.IP "*" 4
46Clusters are marked as used but are not owned by a file. They are marked as free.
47.PP
48Additionally, the following problems are detected, but not repaired:
49.IP "*" 4
50Invalid parameters in boot sector.
51.IP "*" 4
52Absence of . and .. entries in non\-root directories
53.PP
54When \fBdosfsck\fR checks a filesystem, it accumulates all changes in memory and performs them only after all checks are complete. This can be disabled with the \fB\-w\fR option.
55
56.SH OPTIONS
57.IP "\fB\-a\fR" 4
58Automatically repair the filesystem. No user intervention is necessary. Whenever there is more than one method to solve a problem, the least destructive approach is used.
59.IP "\fB\-A\fR" 4
60Use Atari variation of the MS\-DOS filesystem. This is default if \fBdosfsck\fR is run on an Atari, then this option turns off Atari format. There are some minor differences in Atari format: Some boot sector fields are interpreted slightly different, and the special FAT entries for end\-of\-file and bad cluster can be different. Under MS\-DOS 0xfff8 is used for EOF and Atari employs 0xffff by default, but both systems recognize all values from 0xfff8...0xffff as end\-of\-file. MS\-DOS uses only 0xfff7 for bad clusters, where on Atari values 0xfff0...0xfff7 are for this purpose (but the standard value is still 0xfff7).
61.IP "\fB\-d\fR" 4
62Delete the specified file. If more that one file with that name exists, the first one is deleted.
63.IP "\fB\-f\fR" 4
64Salvage unused cluster chains to files. By default, unused clusters are added to the free disk space except in auto mode (\fB\-a\fR).
65.IP "\fB\-l\fR" 4
66List path names of files being processed.
67.IP "\fB\-n\fR" 4
68No\-operation mode: non\-interactively check for errors, but don't write
69anything to the filesystem.
70.IP "\fB\-r\fR" 4
71Interactively repair the filesystem. The user is asked for advice whenever
72there is more than one approach to fix an inconsistency.
73.IP "\fB\-t\fR" 4
74Mark unreadable clusters as bad.
75.IP "\fB\-u\fR" 4
76Try to undelete the specified file. \fBdosfsck\fR tries to allocate a chain of contiguous unallocated clusters beginning with the start cluster of the undeleted file.
77.IP "\fB\-v\fR" 4
78Verbose mode. Generates slightly more output.
79.IP "\fB\-V\fR" 4
80Perform a verification pass. The filesystem check is repeated after the first run. The second pass should never report any fixable errors. It may take considerably longer than the first pass, because the first pass may have generated long list of modifications that have to be scanned for each disk read.
81.IP "\fB\-w\fR" 4
82Write changes to disk immediately.
83.IP "\fB\-y\fR" 4
84Same as \fB\-a\fR (automatically repair filesystem) for compatibility with other fsck tools.
85.PP
86\fBNote:\fR If \fB\-a\fR and \fB\-r\fR are absent, the filesystem is only checked, but not repaired.
87
88.SH "EXIT STATUS"
89.IP "0" 4
90No recoverable errors have been detected.
91.IP "1" 4
92Recoverable errors have been detected or \fBdosfsck\fR has discovered an internal inconsistency.
93.IP "2" 4
94Usage error. \fBdosfsck\fR did not access the filesystem.
95
96.SH FILES
97.IP "fsck0000.rec, fsck0001.rec, ..." 4
98When recovering from a corrupted filesystem, \fBdosfsck\fR dumps recovered data into files named 'fsckNNNN.rec' in the top level directory of the filesystem.
99
100.SH BUGS
101Does not create . and .. files where necessary. Does not remove entirely empty directories. Should give more diagnostic messages. Undeleting files should use a more sophisticated algorithm.
102
103.SH SEE ALSO
104\fBdosfslabel\fR(8)
105.br
106\fBmkdosfs\fR(8)
107
108.SH HOMEPAGE
109More information about \fBdosfsck\fR and \fBdosfstools\fR can be found at <\fIhttp://www.daniel\-baumann.ch/software/dosfstools/\fR>.
110
111.SH AUTHORS
112\fBdosfstools\fR were written by Werner Almesberger <\fIwerner.almesberger@lrc.di.epfl.ch\fR>, Roman Hodek <\fIRoman.Hodek@informatik.uni-erlangen.de\fR>, and others. The current maintainer is Daniel Baumann <\fIdaniel@debian.org\fR>.