![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to fsck.8 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv10dc / man / man8|
Return to fsck.8 CVS log | Up to [Research Unix] / researchv10dc / man / man8 |
1.1 root 1: .TH FSCK 8
2: .CT 1 sa_nonmortals
3: .SH NAME
4: fsck \- file system consistency check and interactive repair
5: .SH SYNOPSIS
6: .B /etc/fsck
7: .B -p
8: [
9: .I special ...
10: ]
11: .br
12: .B /etc/fsck
13: [
14: .B -y
15: ]
16: [
17: .B -n
18: ]
19: [
20: .BI -s X
21: ]
22: [
23: .BI -S X
24: ]
25: [
26: .B -t
27: .I filename
28: ] [
29: .I special ...
30: ]
31: .SH DESCRIPTION
32: .I Fsck
33: inspects the disk filesystems
34: in the named
35: .I special
36: files
37: and repairs inconsistencies.
38: If no files are named,
39: every file system listed in
40: .IR fstab (5)
41: with type 0
42: and a nonzero pass number
43: is checked.
44: .PP
45: Under option
46: .BR -p ,
47: .I fsck
48: runs without intervention,
49: repairing minor inconsistencies
50: and aborting on major ones.
51: This form is usually called from
52: .IR rc (8).
53: If no special files are named,
54: file systems in
55: .I fstab
56: are checked in parallel passes:
57: all file systems with pass number 1
58: are checked simultaneously,
59: then all file systems with pass number 2,
60: and so on until
61: .I fstab
62: is exhausted.
63: .PP
64: Here are the minor ailments
65: repaired automatically
66: under
67: .BR -p :
68: .RS
69: unreferenced inodes;
70: .br
71: wrong link counts in inodes;
72: .br
73: missing blocks in the free list;
74: .br
75: blocks in the free list also in files; and
76: .br
77: counts wrong in the super-block.
78: .RE
79: .PP
80: Other inconsistencies
81: cause
82: .I fsck
83: to abandon the inconsistent file system,
84: and exit with a nonzero status
85: when the current pass finishes.
86: .PP
87: Without the
88: .B -p
89: option,
90: .I fsck
91: inspects one file system at a time,
92: interactively.
93: Each inconsistency causes
94: .I fsck
95: to print a message
96: and ask permission to fix the problem.
97: The operator may require arcane knowledge
98: to guide
99: .I fsck
100: safely through repair of a badly damaged file system.
101: .PP
102: Here are the remaining options.
103: They are allowed only if
104: .B -p
105: is absent.
106: .TP
107: .B -y
108: Assume a yes response to all questions.
109: This should be used with great caution.
110: .TP
111: .B -n
112: Assume a no response to all questions;
113: do not open the file system for writing.
114: This option is assumed if the file system cannot be opened for writing.
115: .TP
116: .BI -s X
117: Ignore the actual free list and (unconditionally) reconstruct a new
118: one by rewriting the super-block of the file system.
119: The file system should be unmounted while this is done; if this
120: is not possible, care should be taken that the system is quiescent
121: and that it is rebooted immediately afterwards.
122: This precaution is necessary so that the old, bad, in-core copy
123: of the superblock will not continue to be used, or written on the file system.
124: If the file system has a bitmap free list (see
125: .IR filsys (5)),
126: the free list is always reconstructed unless the
127: .B -n
128: option is enabled.
129: .IP
130: Parameter
131: .I X
132: allows free-list parameters to be specified:
133: .BI -s blocks-per-cylinder : blocks-to-skip\c
134: \&.
135: If
136: .I X
137: is not given,
138: the values used when the file system was created
139: are used; see
140: .IR mkfs (8).
141: If these values were not specified,
142: .I X
143: is assumed to be
144: .BR 400:9 .
145: .TP
146: .BI -S X
147: Conditionally reconstruct the free list.
148: This option
149: is like
150: .BI -s X
151: except that the free list is rebuilt only
152: if no discrepancies were found.
153: .B -S
154: implies
155: .BR -n .
156: .TP
157: .B -t
158: If
159: .I fsck
160: cannot obtain enough memory to keep its tables,
161: it uses a scratch file.
162: If the
163: .B -t
164: option is
165: specified, the file named in the next argument
166: is used as the scratch file, if needed.
167: Without
168: .BR -t ,
169: .I fsck
170: will prompt the operator for the name of the
171: scratch file.
172: The file chosen should not be on the
173: file system being checked.
174: If it did not already exist,
175: it is removed when
176: .I fsck
177: completes.
178: .PD
179: .br
180: .ne 6
181: .PP
182: Inconsistencies checked are:
183: .IP
184: .nf
185: Blocks claimed more than once.
186: Blocks designated outside the file system.
187: Incorrect link counts.
188: Directory size not 16-byte aligned.
189: Bad inode format.
190: Blocks not accounted for anywhere.
191: Directory entry pointing to unallocated inode.
192: Inode number out of range.
193: More than 65536 inodes.
194: More blocks for inodes than there are in the file system.
195: Bad free block list format.
196: Total free block and/or free inode count incorrect.
197: .fi
198: .PP
199: Orphaned files and directories (allocated but unreferenced) are
200: reconnected by
201: placing them in the directory
202: .F lost+found
203: in the root of the file system being checked.
204: The name assigned is the inode number,
205: prefixed by
206: .LR # .
207: .PP
208: Checking the raw device is almost always faster,
209: but
210: .I fsck
211: distinguishes bitmapped from non-bitmapped file systems
212: by examining the minor device number,
213: so the block device is safer.
214: .SH FILES
215: .F /etc/fstab
216: .SH "SEE ALSO"
217: .IR fstab (5),
218: .IR filsys (5),
219: .IR mkfs (8),
220: .IR reboot (8)
221: .br
222: T. J. Kowalski,
223: `Fsck\(emthe
224: .SM UNIX
225: File System Check Program',
226: this manual, Volume 2
227: .SH BUGS
228: Inode numbers for
229: .B .
230: and
231: .B ..
232: in each directory should be checked for validity.
233: .PP
234: Some systems save core images after a crash
235: in the swap area;
236: on such machines,
237: checking many large file systems in parallel
238: may cause swapping, overwriting the crash dump.
239: It is best just to write crash dumps in a a safer place.
240: If disk space for dumps and swapping is scarce,
241: avoid checking more than three 120-megabyte file systems
242: in parallel on a machine with four megabytes of physical memory.
243: .PP
244: Examining the minor device number is a botch;
245: there should be an explicit flag somewhere.
246: .PP
247: .I Fsck
248: does not have supernatural powers.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.