Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
International Rescue Committe

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 54 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       fsck.minix [ -larvsmf ] device


       fsck.minix  performs  a  consistency  check  for the Linux
       MINIX filesystem.  The current  version  supports  the  14
       character and 30 character filename options.

       The   program   assumes  the  file  system  is  quiescent.
       fsck.minix should not be used on a mounted  device  unless
       you can be sure nobody is writing to it (and remember that
       the kernel can write to it when it searches for files).

       The device will usually have the following form:
              /dev/hda[1-63] (IDE disk 1)
              /dev/hdb[1-63] (IDE disk 2)
              /dev/sda[1-15] (SCSI disk 1)
              /dev/sdb[1-15] (SCSI disk 2)

       If the file system  was  changed  (i.e.,  repaired),  then
       fsck.minix  will  print "FILE SYSTEM HAS CHANGED" and will
       sync(2) three times before exiting.  Since Linux does  not
       currently  have raw devices, there is no need to reboot at
       this time.


       fsck.minix should not be used  on  a  mounted  filesystem.
       Using  fsck.minix  on a mounted filesystem is very danger­
       ous, due to the possibility that deleted files  are  still
       in use, and can seriously damage a perfectly good filesys­
       tem!  If you  absolutely  have  to  run  fsck.minix  on  a
       mounted  filesystem (i.e., the root filesystem), make sure
       nothing is writing to the disk,  and  that  no  files  are
       "zombies" waiting for deletion.


       -l     Lists all filenames

       -r     Performs interactive repairs

       -a     Performs  automatic  repairs  (this  option implies
              -r), and serves to  answer  all  of  the  questions
              asked  with  the  default.   Note  that this can be
              extremely dangerous in the case of  extensive  file
              system damage.

       -v     Verbose

       -s     Outputs super-block information

       -m     Activates MINIX-like "mode not cleared" warnings

       "unable  to  read super block".  If the device exists, but
       is not a MINIX file system,  fsck.minix  will  print  "bad
       magic number in super-block".


       The  exit  code  returned  by fsck.minix is the sum of the

       0      No errors

       3      File system  errors  corrected,  system  should  be
              rebooted if file system was mounted

       4      File system errors left uncorrected

       8      Operational error

       16     Usage or syntax error

       In  point  of fact, only 0, 3, 4, 7, 8, and 16 can ever be


       Linus Torvalds (torvalds@cs.helsinki.fi)
       Error code values by Rik Faith (faith@cs.unc.edu)
       Added support for file system valid  flag:  Dr.  Wettstein
       Check  to  prevent  fsck  of  mounted  filesystem added by
       Daniel Quinlan (quinlan@yggdrasil.com)
       Minix v2 fs support by Andreas Schwab (schwab@issan.infor­
       matik.uni-dortmund.de),   updated   by  Nicolai  Langfeldt
       Portability patch by Russell King (rmk@ecs.soton.ac.uk).

Util-Linux 2.6             2 July 1996                    FSCK(8)
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.10 Seconds