CHUCK(8) CHUCK(8)
NAME
chuck - a file system checking program
SYNOPSIS
/etc/chuck [ option ... ] device
/etc/chuck -M blocks device
/etc/upchuck [ -w ] [ -p program ]
DESCRIPTION
Chuck checks and optionally repairs the file system on the
named device. It is normally invoked by upchuck by rc(8)
during reboots. The -w flag to upchuck is passed on to
program. If program is not present, the default is (Try, as
super-user, /etc/upchuck -p /bin/echo to see the normal
arguments to chuck.) If upchuck can read the raw version of
device, it will, except for the root file system.
The options are
-w Try to do standard repairs.
-b blocksize
Specify file system block size; default is 4096.
-i Interactive. Ask approval for each change.
-I inode ...
-B block ...
Report on inodes or blocks specified by number.
-v Verbose. Give more commentary.
Chuck can also make a new file system: chuck -M size device
makes a bitmapped file system (only) of size 4096-byte
blocks on device. It asks approval before writing.
FILES
SEE ALSO
fstab(5), filsys(5), fsck(8), reboot(8)
BUGS
Chuck does not replace real expertise. It will not automat-
ically repair a file system with duplicate blocks. In com-
plicated situations it may have to be run several times to
get complete consistency.
It will not recover from I/O errors in reading the inodes,
and does not yet extend when necessary.
It uses memory freely (about 12 bytes per file system block
CHUCK(8) CHUCK(8)
and 84 bytes per inode).
Chuck is still experimental, and acts the part. Error mes-
sages are usually inscrutable.
It believes even preposterous super-blocks and consequently
can get core images.