fsck
From Wikipedia, the free encyclopedia
 |
This article needs additional citations for verification. Please help improve this article by adding reliable references (ideally, using inline citations). Unsourced material may be challenged and removed. (April 2007) |
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 Unix and Unix-like operating systems such as Linux.
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 either interactively repairing damaged file systems (the user must decide how to fix specific problems), automatically deciding 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 there is believed to be a problem with the file system. However, running fsck on a mounted file system can potentially cause severe data corruption/loss.
A journaling file system is designed such that tools such as fsck do not need to be run after unclean shutdown (i.e. crash). The UFS2 Filesystem in FreeBSD has background fsck, so it is usually not necessary to wait for fsck to finish before accessing the disk.
The Microsoft equivalent programs are scandisk and chkdsk.
Contents |
[edit] Use as profanity
Before the rise of journaling file systems, it was common for an improperly shut-down Unix system's file system to develop a corrupted superblock. This possibly-serious problem could only be resolved by running fsck, which could take anywhere from a few seconds to hours, depending on the volume's size. Because of the severity of fsck not being able to resolve this error, the terms "fsck" and "fscked" have come into use among Unix system administrators as a minced oath. When one is told "Go fsck yourself!" the meaning implied is to "go away, analyze yourself, and fix your problems", mirroring fsck's primary function.
It is unclear whether this usage was cause or effect, as it has been anecdotally reported that Dennis Ritchie has claimed "The second letter was originally different." [1]
[edit] Pronunciation
Like many computer jargon terms without vowels, fsck is essentially unpronounceable in most languages and so people are forced to improvise when speaking it aloud. It can be pronounced "F-S-C-K", "F-S-check", "F-sack", "fisk", "fizik", "fuss-uck", "fizz-uck", "fozz-uck", "F-sick", "F-suck" (associated with how long it takes to run [2]), "F-sek" or "fusk".
[edit] Example
fsck /dev/sdb1
[edit] See also
- List of Unix programs
- List of file systems
- e2fsprogs, which includes the e2fsck utility standard on many Linux distributions
[edit] References
[edit] External links
- man fsck
- Checking and Repairing File system with fsck
- Jargon File entry: fscking
- The many faces of fsck
- System Management Concepts: Fsck Commands Reference, Volume 2
|
||||||||||||||||||||||||||
