fsck

The system utility fsck (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, macOS, and FreeBSD.[1] A similar command, CHKDSK, exists in Microsoft Windows and (its ancestor) MS-DOS.

For the album by Farmers Manual, see Fsck (album).

fsck
fsck in action on a Linux system.
Operating systemUnix and Unix-like
TypeCommand

Pronunciation

There is no agreed pronunciation. It can be pronounced "F-S-C-K", "F-S-check", "fizz-check", "F-sack", "fisk", "fishcake", "fizik", "F-sick", "F-sock", "F-sek", "feshk" the sibilant "fsk", "fix", "farsk" or "fusk".[2]

Use

Generally, fsck is run either automatically at boot time, or manually by the system administrator. The command works directly on data structures stored on disk, which are internal and specific to the particular file system in use - so an fsck command tailored to the file system is generally required. The exact behaviors of various fsck implementations vary, but they typically follow a common order of internal operations and provide a common command-line interface to the user.

Most 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 does not have to answer any questions), or reviewing the problems that need to be resolved on a file system without actually fixing them. Partially recovered files where the original file name cannot be reconstructed are typically recovered to a "lost+found" directory that is stored at the root of the file system.

A system administrator can also run fsck manually if they believe there is a problem with the file system. The file system is normally checked while unmounted, mounted read-only, or with the system in a special maintenance mode.

Modern journaling file systems are designed such that tools such as fsck do not need to be run after unclean shutdown (i.e. crash). The UFS2 file system in FreeBSD has a background fsck, so it is usually not necessary to wait for fsck to finish before accessing the disk. Full copy-on-write file systems such as ZFS and Btrfs are designed to avoid most causes of corruption and have no traditional "fsck" repair tool. Both have a "scrub" utility which examines and repairs any problems; in the background and on a mounted file system.

The equivalent programs on Microsoft Windows and MS-DOS are CHKDSK and SCANDISK.

As an expletive

The severity of file system corruption led to the terms "fsck" and "fscked" becoming used among Unix system administrators as a minced oath for "fuck" and "fucked".[3] It is unclear whether this usage was cause or effect, as a report from a question and answer session at USENIX 1998 claims that "fsck" originally had a different name:

Dennis Ritchie: “So fsck was originally called something else”
Question: “What was it called?”
Dennis Ritchie: "Well, the second letter was different"[4][5]

"Go fsck yourself", is occasionally used online as an injunction to a person to go and correct their issue (attitude, ignorance of the subject matter, etc.) - in the same way that running fsck involves fixing fundamental errors.

Examples

The following example checks the file system configured to be mounted on /usr partition; the file system needs to be unmounted first:

 fsck /usr

The following example checks the Linux JFS file system on a mdadm software RAID device:

 fsck -t jfs /dev/md0
gollark: Anyway, I *do* know when the rounds will end, so if I felt so inclined I could probably mathize™ and work out the optimal time to distinguish grudger/TFT/angel.
gollark: Mind control should be included in ALL IPD analyses.
gollark: Huh, it looks like that... might actually be possible?
gollark: Unfortunately, I can't distinguish grudger/TFT/angel without possibly invoking the wrath of the grudger.
gollark: I was thinking about trying to patternmatch different player types.

See also

References
  1. "fsck(8) - Linux man page". die.net. Retrieved 7 May 2013.
  2. "running "fuck" twice almost gave me a heartattack · Issue #1 · nvbn/thefuck". GitHub.
  3. Raymond, Eric S (September 24, 1999). "fscking". The Jargon File. Archived from the original on 2009-01-03. fcking: /fus'-king/ or /eff'-seek-ing/ adj. [Usenet; common] Fucking, in the expletive sense (it refers to the Unix filesystem-repair command fsck(1), of which it can be said that if you have to use it at all you are having a bad day). Originated on {scary devil monastery} and the bofh.net newsgroups, but became much more widespread following the passage of {CDA}. Also occasionally seen in the variant ‘What the fsck?’
  4. Crosby, Matthew. "Report from Usenix". alt.sysadmin.recovery. Usenet. Retrieved 2016-02-20.
  5. "Mind Fsck". WikiWikiWeb. C2.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.