1fsck_pcfs(1M) System Administration Commands fsck_pcfs(1M)
2
6 fsck_pcfs - file system consistency check and interactive repair
7
9 fsck -F pcfs [generic_options] special
10 fsck -F pcfs [generic_options] [-o specific_options] special
13
16 The fsck utility audits and interactively repairs inconsistent condi‐
17 tions on file systems. special represents the character special device
18 on which the file system resides, for example /dev/rdiskette. The char‐
19 acter special device, not the block special device, should be used.
20 In the case of correcting serious inconsistencies, by default, fsck
23 asks for confirmation before making a repair and waits for the operator
24 to respond either yes or no. If the operator does not have write per‐
25 mission on the file system, fsck defaults to a -n (no corrections)
26 action. See fsck(1M).
27 Repairing some file system inconsistencies may result in loss of data.
30 The amount and severity of data loss may be determined from the diag‐
31 nostic output.
32 When executed with the verify option (-o v), fsck_pcfs automatically
35 scans the entire file system to verify that all of its allocation units
36 are accessible. If it finds any units inaccessible, it updates the file
37 allocation table (FAT) appropriately. It also updates any effected
38 directory entries to reflect the problem. This directory update
39 includes truncating the file at the point in its allocation chain where
40 the file data is no longer accessible. Any remaining accessible alloca‐
41 tion units become orphaned.
42 Orphaned chains of accessible allocation units are, with the operator's
45 concurrence, linked back into the file system as files in the root
46 directory. These files are assigned names of the form fileNNNN.chk,
47 where the Ns are digits in the integral range from 0 through 9.
48 After successfully scanning and correcting any errors in the file sys‐
51 tem, fsck displays a summary of information about the file system. This
52 summary includes the size of the file system in bytes, the number of
53 bytes used in directories and individual files, and the number of
54 available allocation units remaining in the file system.
55
57 generic_options The following generic options are supported:
58 -m Check but do not repair. This option
60 checks that the file system is suit‐
61 able for mounting, returning the
62 appropriate exit status. If the file
63 system is ready for mounting, fsck
64 displays a message such as:
65 pcfs fsck: sanity check:
67 /dev/rdiskette okay
68 -n | -N Assume a no response to all ques‐
73 tions asked by fsck; do not open
74 the file system for writing.
75 -V Echo the expanded command line, but
78 do not execute the command. This
79 option may be used to verify and to
80 validate the command line.
81 -y | -Y Assume a yes response to all ques‐
84 tions asked by fsck.
85 -o specific_options Specify pcfs file system specific options in a
89 comma-separated list, in any combination, with
90 no intervening spaces.
91 v Verify all allocation units are accessible
93 prior to correcting inconsistencies in the
94 metadata.
95 p Check and fix the file system non-interac‐
98 tively (preen). Exit immediately if there
99 is a problem requiring intervention.
100 w Check writable file systems only.
103
107 special The device which contains the pcfs. The device name for a
108 diskette is specified as /dev/rdiskette0 for the first
109 diskette drive, or /dev/rdiskette1 for a second diskette
110 drive. A hard disk device or high-capacity removable device
111 name much be qualified with a suffix to indicate the proper
112 FDISK partition.
113 For example, in the names: /dev/rdsk/c0t0d0p0:c and
115 /dev/rdsk/c0t4d0s2:c, the :c suffix indicates the first par‐
116 tition on the disk contains the pcfs.
117
120 See attributes(5) for descriptions of the following attributes:
121 ┌─────────────────────────────┬─────────────────────────────┐
126 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
127 ├─────────────────────────────┼─────────────────────────────┤
128 │Availability │SUNWesu │
129 ├─────────────────────────────┼─────────────────────────────┤
130 │Interface Stability │Stable │
131 └─────────────────────────────┴─────────────────────────────┘
132
134 fsck(1M), fstyp(1M), fdisk(1M), mkfs(1M), mkfs_pcfs(1M), mountall(1M),
135 attributes(5), pcfs(7FS),
136
138 The operating system buffers file system data. Running fsck on a
139 mounted file system can cause the operating system's buffers to become
140 out of date with respect to the disk. For this reason, the file system
141 should be unmounted when fsck is used. If this is not possible, care
142 should be taken that the system is quiescent and that it is rebooted
143 immediately after fsck is run. Quite often, however, this is not suffi‐
144 cient. A panic will probably occur if running fsck on a file system
145 modifies the file system.
146SunOS 5.11 28 Jan 2000 fsck_pcfs(1M)