blob: 087b6d50d4c5ad7f63de90c2774d6ac3bc9f9eae (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
|
.TH CHUCK 8
.CT 1 sa_nonmortals
.SH NAME
chuck \- a file system checking program
.SH SYNOPSIS
.B /etc/chuck
[
.I option ...
]
.I device
.PP
.B /etc/chuck
.B -M
.I blocks
.I device
.PP
.B /etc/upchuck
[
.B -w
] [
.B -p
.I program
]
.SH DESCRIPTION
.PP
.I Chuck
checks and optionally repairs the file system on the named
.I device.
It is normally invoked by
.I upchuck
by
.IR rc (8)
during reboots.
The
.B -w
flag to
.I upchuck
is passed on to
.I program.
If
.I program
is not present, the default is
.FR /etc/chuck .
(Try, as super-user,
.B "/etc/upchuck -p /bin/echo
to see the normal arguments to
.IR chuck .)
If
.I upchuck
can read the raw version of
.I device,
it will, except for the root file system.
.PP
The options are
.TP
.B -w
Try to do standard repairs.
.TP
.BI -b " blocksize
Specify file system block size; default is 4096.
.TP
.B -i
Interactive.
Ask approval for each change.
.TP
.BI -I " inode ...
.br
.ns
.TP
.BI -B " block ...
Report on inodes or blocks specified by number.
.TP
.B -v
Verbose.
Give more commentary.
.PP
.I Chuck
can also make a new file system:
.B "chuck -M"
.I size device
makes a bitmapped file system (only)
of
.I size
4096-byte blocks
on
.IR device .
It asks approval before writing.
.SH FILES
.F /etc/fstab
.SH "SEE ALSO"
.IR fstab (5),
.IR filsys (5),
.IR fsck (8),
.IR reboot (8)
.SH BUGS
.I Chuck
does not replace real expertise.
It will not automatically repair a file system with duplicate blocks.
In complicated situations it may have to be run
several times to get complete consistency.
.br
It will not recover from I/O errors in reading the inodes,
and does not yet extend
.F lost+found
when necessary.
.br
It uses memory freely (about 12 bytes per file system block
and 84 bytes per inode).
.br
.I Chuck
is still experimental,
and acts the part.
Error messages are usually inscrutable.
.br
It believes even preposterous super-blocks and
consequently can get core images.
|
