Print this page
6198 Let's EOL cachefs
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1m/fsck.1m.man.txt
+++ new/usr/src/man/man1m/fsck.1m.man.txt
1 1 FSCK(1M) Maintenance Commands FSCK(1M)
2 2
3 3
4 4
5 5 NAME
6 6 fsck - check and repair file systems
7 7
8 8 SYNOPSIS
9 9 fsck [-F FSType] [-m] [-V] [-v] [special]...
10 10
11 11
12 12 fsck [-F FSType] [-n | N | y | Y] [-V] [-v]
13 13 [-o FSType-specific-options] [special]...
14 14
15 15
16 16 DESCRIPTION
17 17 fsck audits and interactively repairs inconsistent file system
18 18 conditions. If the file system is inconsistent the default action for
19 19 each correction is to wait for the user to respond yes or no. If the
20 20 user does not have write permission fsck defaults to a no action. Some
21 21 corrective actions will result in loss of data. The amount and severity
22 22 of data loss can be determined from the diagnostic output.
23 23
24 24
25 25 FSType-specific-options are options specified in a comma-separated (with
26 26 no intervening spaces) list of options or keyword-attribute pairs for
27 27 interpretation by the FSType-specific module of the command.
28 28
29 29
30 30 special represents the character special device on which the file
31 31 system resides, for example, /dev/rdsk/c1t0d0s7. Note: the character
32 32 special device, not the block special device, should be used. fsck will
33 33 not work if the block device is mounted.
34 34
35 35
36 36 If no special device is specified fsck checks the file systems listed
37 37 in /etc/vfstab. Those entries in /etc/vfstab which have a character
38 38 special device entry in the fsckdev field and have a non-zero numeric
39 39 entry in the fsckpass field will be checked. Specifying -F FSType limits
40 40 the file systems to be checked to those of the type indicated.
41 41
42 42
43 43 If special is specified, but -F is not, the file system type will be
44 44 determined by looking for a matching entry in /etc/vfstab. If no entry
45 45 is found, the default local file system type specified in
46 46 /etc/default/fs will be used.
47 47
48 48
49 49 If a file system type supports parallel checking, for example, ufs,
50 50 some file systems eligible for checking may be checked in parallel.
51 51 Consult the file system-specific man page (for example, fsck_ufs(1M))
52 52 for more information.
53 53
54 54 OPTIONS
55 55 The following generic options are supported:
56 56
57 57 -F FSType
58 58 Specify the file system type on which to operate.
59 59
60 60
61 61 -m
62 62 Check but do not repair. This option checks that the file system is
63 63 suitable for mounting, returning the appropriate exit status. If
64 64 the file system is ready for mounting, fsck displays a message such
65 65 as:
66 66
67 67 ufs fsck: sanity check: /dev/rdsk/c0t3d0s1 okay
68 68
69 69
70 70
71 71
72 72 -n | -N
73 73 Assume a no response to all questions asked by fsck; do not open
74 74 the file system for writing.
75 75
76 76
77 77 -V
78 78 Echo the expanded command line but do not execute the command. This
79 79 option may be used to verify and to validate the command line.
80 80
81 81
82 82 -v
83 83 Enables verbose output. Might not be supported by all filesystem-
84 84 specific fsck implementations.
85 85
86 86
87 87 -y | Y
88 88 Assume a yes response to all questions asked by fsck.
89 89
90 90
91 91 -o specific-options
92 92 These specific-options can be any combination of the following
93 93 separated by commas (with no intervening spaces).
94 94
95 95 b=n
96 96 Use block n as the super block for the file system. Block 32 is
97 97 always one of the alternate super blocks. Determine the
98 98 location of other super blocks by running newfs(1M) with the -Nv
99 99 options specified.
100 100
101 101
102 102 c
103 103 If the file system is in the old (static table) format, convert
104 104 it to the new (dynamic table) format. If the file system is in
105 105 the new format, convert it to the old format provided the old
106 106 format can support the file system configuration. In
107 107 interactive mode, fsck will list the direction the conversion
108 108 is to be made and ask whether the conversion should be done. If
109 109 a negative answer is given, no further operations are done on
110 110 the file system. In preen mode, the direction of the conversion
111 111 is listed and done if possible without user interaction.
112 112 Conversion in preen mode is best used when all the file systems
113 113 are being converted at once. The format of a file system can be
114 114 determined from the first line of output from fstyp(1M). Note:
115 115 the c option is seldom used and is included only for
116 116 compatibility with pre-4.1 releases. There is no guarantee that
117 117 this option will be included in future releases.
118 118
119 119
120 120 f
121 121 Force checking of file systems regardless of the state of their
122 122 super block clean flag.
123 123
124 124
125 125 p
126 126 Check and fix the file system non-interactively ("preen"). Exit
127 127 immediately if there is a problem requiring intervention. This
128 128 option is required to enable parallel file system checking.
129 129
130 130
131 131 w
132 132 Check writable file systems only.
133 133
134 134
135 135
136 136 EXIT STATUS
137 137 0
138 138 file system is unmounted and OK
139 139
140 140
141 141 1
142 142 erroneous parameters are specified
143 143
144 144
145 145 32
146 146 file system is unmounted and needs checking (fsck -m only)
147 147
148 148
149 149 33
150 150 file system is already mounted
151 151
152 152
153 153 34
154 154 cannot stat device
155 155
156 156
157 157 35
158 158 a filesystem that is mounted read/write was modified - reboot
159 159
160 160
161 161 36
162 162 uncorrectable errors detected - terminate normally
163 163
164 164
165 165 37
166 166 a signal was caught during processing
167 167
168 168
169 169 39
170 170 uncorrectable errors detected - terminate immediately
171 171
172 172
173 173 40
174 174 file system is mounted read-only and is OK
175 175
176 176
177 177 USAGE
178 178 The fsck command is large file aware for UFS file systems, per the
179 179 largefile(5) man page.
180 180
181 181 FILES
182 182 /etc/default/fs
183 183 default local file system type. Default values can be set for the
184 184 following flags in /etc/default/fs. For example: LOCAL=ufs.
185 185
186 186 LOCAL
187 187 The default partition for a command if no FSType is specified.
188 188
189 189
190 190
191 191 /etc/vfstab
192 192 list of default parameters for each file system
193 193
194 194
195 195 ATTRIBUTES
196 196 See attributes(5) for descriptions of the following attributes:
197 197
|
↓ open down ↓ |
197 lines elided |
↑ open up ↑ |
198 198
199 199
200 200
201 201 +--------------------+-----------------+
202 202 | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
203 203 +--------------------+-----------------+
204 204 |Interface Stability | Committed |
205 205 +--------------------+-----------------+
206 206
207 207 SEE ALSO
208 - clri(1M), fsck_cachefs(1M), fsck_ufs(1M), fsdb_ufs(1M), fsirand(1M),
209 - fstyp(1M), mkfs(1M), mkfs_ufs(1M), mountall(1M), newfs(1M), reboot(
210 - 1M), vfstab(4), attributes(5), largefile(5), ufs(7FS)
208 + clri(1M), fsck_ufs(1M), fsdb_ufs(1M), fsirand(1M), fstyp(1M), mkfs(1M),
209 + mkfs_ufs(1M), mountall(1M), newfs(1M), reboot( 1M), vfstab(4),
210 + attributes(5), largefile(5), ufs(7FS)
211 211
212 212 WARNINGS
213 213 The operating system buffers file system data. Running fsck on a
214 214 mounted file system can cause the operating system's buffers to become
215 215 out of date with respect to the disk. For this reason, the file system
216 216 should be unmounted when fsck is used. If this is not possible, care
217 217 should be taken that the system is quiescent and that it is rebooted
218 218 immediately after fsck is run. Quite often, however, this will not be
219 219 sufficient. A panic will probably occur if running fsck on a file
220 220 system modifies the file system.
221 221
222 222 NOTES
223 223 This command may not be supported for all FSTypes.
224 224
225 225
226 226 Starting with Solaris 9, fsck manages extended attribute data on the
227 227 disk. (See fsattr(5) for a description of extended file attributes.) A
228 228 file system with extended attributes can be mounted on versions of
229 229 Solaris that are not attribute-aware (versions prior to Solaris 9), but
|
↓ open down ↓ |
9 lines elided |
↑ open up ↑ |
230 230 the attributes will not be accessible and fsck will strip them from the
231 231 files and place them in lost+found. Once the attributes have been
232 232 stripped, the file system is completely stable on versions of Solaris
233 233 that are not attribute-aware, but would be considered corrupted on
234 234 attribute-aware versions. In the latter circumstance, run the attribute-
235 235 aware fsck to stabilize the file system before using it in an
236 236 attribute-aware environment.
237 237
238 238
239 239
240 - May 7, 2008 FSCK(1M)
240 + September 8, 2015 FSCK(1M)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX