Penguin
Blame: fsck.minix(8)
EditPageHistoryDiffInfoLikePages
Annotated edit history of fsck.minix(8) version 2, including all changes. View license author blame.
Rev Author # Line
1 perry 1 FSCK
2 !!!FSCK
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 WARNING
7 OPTIONS
8 SEE ALSO
9 DIAGNOSTICS
10 EXIT CODES
11 AUTHOR
12 ----
13 !!NAME
14
15
16 fsck.minix - a file system consistency checker for Linux
17 !!SYNOPSIS
18
19
20 __fsck.minix [[ -larvsmf ]__ device
21 !!DESCRIPTION
22
23
24 __fsck.minix__ performs a consistency check for the Linux
25 MINIX filesystem. The current version supports the 14
26 character and 30 character filename options.
27
28
29 The program assumes the file system is quiescent.
30 __fsck.minix__ should not be used on a mounted device
31 unless you can be sure nobody is writing to it (and remember
32 that the kernel can write to it when it searches for
33 files).
34
35
36 The device will usually have the following
37 form:
38
39
40 /dev/hda[[1-63] (IDE disk 1)
41 /dev/hdb[[1-63] (IDE disk 2)
42 /dev/sda[[1-15] (SCSI disk 1)
43 /dev/sdb[[1-15] (SCSI disk 2)
44 If the file system was changed (i.e., repaired), then __fsck.minix__ will print sync(2) three times before exiting. Since Linux does not currently have raw devices, there is ''no'' need to reboot at this time.
45 !!WARNING
46
47
48 __fsck.minix__ should __not__ be used on a mounted
49 filesystem. Using __fsck.minix__ on a mounted filesystem
50 is very dangerous, due to the possibility that deleted files
51 are still in use, and can seriously damage a perfectly good
52 filesystem! If you absolutely have to run __fsck.minix__
53 on a mounted filesystem (i.e., the root filesystem), make
54 sure nothing is writing to the disk, and that no files are
55 __
56 !!OPTIONS
57
58
59 __-l__
60
61
62 Lists all filenames
63
64
65 __-r__
66
67
68 Performs interactive repairs
69
70
71 __-a__
72
73
74 Performs automatic repairs (this option implies __-r__),
75 and serves to answer all of the questions asked with the
76 default. Note that this can be extremely dangerous in the
77 case of extensive file system damage.
78
79
80 __-v__
81
82
83 Verbose
84
85
86 __-s__
87
88
89 Outputs super-block information
90
91
92 __-m__
93
94
95 Activates MINIX-like
96
97
98 __-f__
99
100
101 Force file system check even if the file system was marked
102 as valid (this marking is done by the kernel when the file
103 system is unmounted).
104 !!SEE ALSO
105
106
2 perry 107 fsck(8), fsck.ext(8), __fsck.ext2__(8),
108 fsck.xiafs(8), mkfs(8), __mkfs.minix__(8),
109 mkfs.ext(8), __mkfs.ext2__(8),
110 mkfs.xiafs(8). reboot(8)
1 perry 111 !!DIAGNOSTICS
112
113
114 There are numerous diagnostic messages. The ones mentioned
115 here are the most commonly seen in normal
116 usage.
117
118
119 If the device does not exist, __fsck.minix__ will print
120 __fsck.minix__
121 will print
122 __
123 !!EXIT CODES
124
125
126 The exit code returned by __fsck.minix__ is the sum of
127 the following:
128
129
130 0
131
132
133 No errors
134
135
136 3
137
138
139 File system errors corrected, system should be rebooted if
140 file system was mounted
141
142
143 4
144
145
146 File system errors left uncorrected
147
148
149 8
150
151
152 Operational error
153
154
155 16
156
157
158 Usage or syntax error
159
160
161 In point of fact, only 0, 3, 4, 7, 8, and 16 can ever be
162 returned.
163 !!AUTHOR
164
165
166 Linus Torvalds (torvalds@cs.helsinki.fi)
167 Error code values by Rik Faith (faith@cs.unc.edu)
168 Added support for file system valid flag: Dr. Wettstein
169 (greg%wind.uucp@plains.nodak.edu)
170 Check to prevent fsck of mounted filesystem added by Daniel
171 Quinlan (quinlan@yggdrasil.com)
172 Minix v2 fs support by Andreas Schwab
173 (schwab@issan.informatik.uni-dortmund.de), updated by
174 Nicolai Langfeldt (janl@math.uio.no)
175 Portability patch by Russell King
176 (rmk@ecs.soton.ac.uk).
177 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.