Fsck
|
|
- The title of this article is incorrect because of technical limitations. The correct title is fsck.
The system utility fsck (for "file system check" or "file system consistency check") is a tool for checking the consistency of a file system in the Unix system and clones thereof.
A journaling file system is designed such that tools such as fsck do not need to be run as often. The UFS2 Filesystem in FreeBSD has background fsck, so it is usually not necessary to wait for fsck to finish before accessing the disk.
Generally, fsck is run automatically at boot time when the system detects that a file system is in an inconsistent state, indicating a non-graceful shutdown, such as a crash or power loss. Typically, fsck utilities provide options for interactively repairing damaged file systems (the user must decide how to fix specific problems), allowing fsck to decide how to fix specific problems (so the user doesn't have to answer any questions), or reviewing the problems that need to be resolved on a file system without actually fixing them.
Fsck can also be run manually by the system administrator if he believes there is a problem with the file system.
The term 'fsck' has come into use among UNIX system administrators as a written euphemism of 'fuck'. Spoken, it can be pronounced "F-S-C-K", "F-S-check", "F-sock", "fisk", "fizik", "fsick", or even "F-suck".
The Microsoft equivalent programs are scandisk and chkdsk. In DOS, chkdsk was used to check file system integrity, but later versions also featured a tool called scandisk for checking disk surface for bad clusters. Windows 95, Windows 98 and Windows Me featured a version of scandisk which ran natively in the Windows envionment. The Windows NT series, including NT 4, Windows 2000, and Windows XP all use a modern, updated version of chkdsk which performs both disk surface and file system scanning.
See also
- List of Unix programs
- man fsck (http://www.hmug.org/man/8/fsck.php)