Seth Woolley's Man Viewer

fsck(8) - e2fsck, fsck, fsck.minix, fsck.xfs, fsck.minix, fsck.reiser4, fsck.xfs, jfs_fsck - initiate replay of the JFS transaction log, and check and repair a JFS formatted device - man 8 fsck

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

FSCK(8)                                                                FSCK(8)

       fsck - check and repair a Linux file(1,n) system

       fsck  [  -sACVRTNP  ]  [ -t fstype ] [filesys ... ] [--] [ fs-specific-
       options ]

       fsck is used to check and optionally repair one or more Linux file(1,n) sys-
       tems.   filesys  can  be  a device name (e.g.  /dev/hdc1, /dev/sdb2), a
       mount(2,8) point (e.g.  /, /usr, /home), or an ext2 label or UUID  specifier
       (e.g.   UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root).  Nor-
       mally, the fsck program will try to run filesystems on different physi-
       cal disk drives in(1,8) parallel to reduce total amount time(1,2,n) to check all of
       the filesystems.

       If no filesystems are specified on the command line, and the -A  option
       is  not  specified,  fsck  will  default  to  checking  filesystems  in(1,8)
       /etc/fstab serial.  This is equivalent to the -As options.

       The exit(3,n,1 builtins) code returned by fsck is the sum of the following conditions:
            0    - No errors
            1    - File system errors corrected
            2    - System should be rebooted
            4    - File system errors left uncorrected
            8    - Operational error(8,n)
            16   - Usage or syntax error(8,n)
            32   - Fsck canceled by user request
            128  - Shared library error(8,n)
       The exit(3,n,1 builtins) code returned when multiple file(1,n) systems are  checked  is  the
       bit-wise OR of the exit(3,n,1 builtins) codes for each file(1,n) system that is checked.

       In  actuality,  fsck  is simply a front-end for the various file(1,n) system
       checkers (fsck.fstype) available under Linux.  The file(1,n) system-specific
       checker  is  searched for in(1,8) /sbin first, then in(1,8) /etc/fs and /etc, and
       finally in(1,8) the directories listed in(1,8)  the  PATH  environment  variable.
       Please  see  the  file(1,n) system-specific checker manual pages for further

       -s     Serialize fsck operations.  This is  a  good  idea  if(3,n)  you  are
              checking  multiple filesystems and the checkers are in(1,8) an inter-
              active mode.  (Note: e2fsck(8) runs in(1,8) an  interactive  mode  by
              default.   To  make e2fsck(8) run in(1,8) a non-interactive mode, you
              must either specify the -p or -a option, if(3,n) you wish for  errors
              to  be corrected automatically, or the -n option if(3,n) you do not.)

       -t fslist
              Specifies the type(s) of file(1,n) system to be checked.  When the -A
              flag  is  specified,  only  filesystems  that  match  fslist are
              checked.  The fslist parameter  is  a  comma-separated  list  of
              filesystems  and  options specifiers.  All of the filesystems in(1,8)
              this comma-separated list may be prefixed by a negation operator
              'no'  or  '!',  which  requests  that only those filesystems not
              listed in(1,8) fslist will be checked.  If all of the filesystems  in(1,8)
              fslist  are not prefixed by a negation operator, then only those
              filesystems listed in(1,8) fslist will be checked.

              Options specifiers  may  be  included  in(1,8)  the  comma  separated
              fslist.   They  must  have  the  format  opts=fs-option.   If an
              options specifier is present, then only filesystems  which  con-
              tain  fs-option  in(1,8) their mount(2,8) options field of /etc/fstab will
              be checked.  If the options specifier is prefixed by a  negation
              operator, then only those filesystems that do not have fs-option
              in(1,8) their mount(2,8) options field of /etc/fstab will be checked.

              For example, if(3,n) opts=ro appears in(1,8) fslist, then only filesystems
              listed in(1,8) /etc/fstab with the ro option will be checked.

              For compatibility with Mandrake distributions whose boot scripts
              depend upon an unauthorized UI change to the fsck program, if(3,n)  a
              filesystem  type of loop is found in(1,8) fslist, it is treated as if(3,n)
              opts=loop were specified as an argument to the -t option.

              Normally, the  filesystem  type  is  deduced  by  searching  for
              filesys  in(1,8)  the  /etc/fstab  file(1,n)  and  using the corresponding
              entry.  If the type can not be deduced, and there is only a sin-
              gle  filesystem given as an argument to the -t option, fsck will
              use the specified filesystem type.  If this type is  not  avail-
              able,  then  the  default  file(1,n)  system type (currently ext2) is

       -A     Walk through the /etc/fstab file(1,n) and try to check all file(1,n)  sys-
              tems in(1,8) one run.  This option is typically used from the /etc/rc
              system initalization file(1,n),  instead  of  multiple  commands  for
              checking a single file(1,n) system.

              The  root  filesystem will be checked first unless the -P option
              is specified (see  below).   After  that,  filesystems  will  be
              checked  in(1,8)  the  order  specified  by the fs_passno (the sixth)
              field in(1,8) the /etc/fstab  file.   Filesystems  with  a  fs_passno
              value  of 0 are skipped and are not checked at all.  Filesystems
              with a fs_passno value of greater than zero will be  checked  in(1,8)
              order,  with  filesystems with the lowest fs_passno number being
              checked first.  If there are multiple filesystems with the  same
              pass  number,  fsck  will  attempt  to  check  them in(1,8) parallel,
              although it will avoid running multiple filesystem checks on the
              same physical disk.

              Hence, a very common configuration in(1,8) /etc/fstab files is to set(7,n,1 builtins)
              the root filesystem to have a fs_passno value of 1  and  to  set(7,n,1 builtins)
              all filesystems to have a fs_passno value of 2.  This will allow
              fsck to automatically run filesystem checkers in(1,8) parallel if(3,n)  it
              is  advantageous  to  do so.  System administrators might choose
              not to use this configuration if(3,n) they  need  to  avoid  multiple
              filesystem  checks  running  in(1,8) parallel for some reason --- for
              example, if(3,n) the machine in(1,8) question is short on memory  so  that
              excessive paging is a concern.

       -C     Display  completion/progress bars for those filesystems checkers
              (currently only for ext2) which support them.   Fsck will manage
              the  filesystem checkers so that only one of them will display a
              progress bar at a time.

       -N     Don't execute, just show what would be done.

       -P     When the -A flag is set(7,n,1 builtins), check the root filesystem  in(1,8)  parallel
              with the other filesystems.  This is not the safest thing in(1,8) the
              world to do, since if(3,n) the root filesystem  is  in(1,8)  doubt  things
              like  the  e2fsck(8) executable might be corrupted!  This option
              is mainly provided for those sysadmins who don't want to  repar-
              tition  the  root  filesystem  to be small and compact (which is
              really the right solution).

       -R     When checking all file(1,n) systems with the -A flag, skip  the  root
              file(1,n) system (in(1,8) case it's already mounted read-write).

       -T     Don't show the title on startup.

       -V     Produce  verbose output, including all file(1,n) system-specific com-
              mands that are executed.

              Options which are not understood  by  fsck  are  passed  to  the
              filesystem-specific  checker.   These  arguments  must  not take
              arguments, as there is no way for fsck to be  able  to  properly
              guess which arguments take options and which don't.

              Options  and  arguments  which follow the -- are treated as file(1,n)
              system-specific options to be passed to the file(1,n) system-specific

              Please  note  that fsck is not designed to pass arbitrarily com-
              plicated options to  filesystem-specific  checkers.   If  you're
              doing something complicated, please just execute the filesystem-
              specific checker directly.  If you pass fsck some horribly  com-
              plicated  option  and  arguments,  and  it  doesn't  do what you
              expect, don't bother reporting it as a bug.  You're almost  cer-
              tainly doing something that you shouldn't be doing with fsck.

       Options  to  different filesystem-specific fsck's are not standardized.
       If in(1,8) doubt, please consult the man(1,5,7) pages  of  the  filesystem-specific
       checker.   Although not guaranteed, the following options are supported
       by most file(1,n) system checkers:

       -a     Automatically repair the file(1,n) system without any questions  (use
              this  option with caution).  Note that e2fsck(8) supports -a for
              backwards compatibility only.  This option is mapped to e2fsck's
              -p  option  which is safe to use, unlike the -a option that some
              file(1,n) system checkers support.

       -n     For some filesystem-specific checkers, the -n option will  cause
              the fs-specific fsck to avoid attempting to repair any problems,
              but simply report such problems to stdout.  This is however  not
              true  for  all  filesystem-specific  checkers.   In  particular,
              fsck.reiserfs(8) will not report any corruption  if(3,n)  given  this
              option.  fsck.minix(8) does not support the -n option at all.

       -r     Interactively  repair  the  filesystem  (ask for confirmations).
              Note: It is generally a bad idea to use this option if(3,n)  multiple
              fsck's  are  being  run  in(1,8)  parallel.   Also  note that this is
              e2fsck's default behavior; it supports this option for backwards
              compatibility reasons only.

       -y     For  some filesystem-specific checkers, the -y option will cause
              the fs-specific fsck to  always  attempt  to  fix  any  detected
              filesystem corruption automatically.  Sometimes an expert may be
              able to do better driving the fsck manually.  Note that not  all
              filesystem-specific checkers implement this option.  In particu-
              lar fsck.minix(8) and fsck.cramfs(8) does  not  support  the  -y
              option as of this writing.

       Theodore Ts'o (


       The  fsck  program's  behavior is affected by the following environment

              If this environment variable is set(7,n,1 builtins), fsck will  attempt  to  run
              all  of  the  specified  filesystems  in(1,8) parallel, regardless of
              whether the filesystems appear to be on the same device.   (This
              is  useful  for RAID systems or high-end storage systems such as
              those sold by companies such as IBM or EMC.)

              This environment variable will limit the maximum number of  file(1,n)
              system  checkers  that  can be running at one time.  This allows
              configurations which have a large number of disks to avoid  fsck
              starting  too  many  file(1,n)  system  checkers at once, which might
              overload CPU and memory resources available on the  system.   If
              this value is zero, then an unlimited number of processes can be
              spawned.  This is currently the default, but future versions  of
              fsck may attempt to automatically determine how many file(1,n) system
              checks can be run based on gathering accounting  data  from  the
              operating system.

       PATH   The PATH environment variable is used to find file(1,n) system check-
              ers.  A set(7,n,1 builtins) of system directories  are  searched  first:  /sbin,
              /sbin/fs.d, /sbin/fs, /etc/fs, and /etc.  Then the set(7,n,1 builtins) of direc-
              tories found in(1,8) the PATH environment are searched.

              This environment variable allows  the  system  administrator  to
              override  the  standard  location of the /etc/fstab file.  It is
              also use for developers who are testing fsck.

       fstab(5),   mkfs(8),    fsck.ext2(8)    or    e2fsck(8),    cramfsck(8)
       fsck.minix(8), fsck.jfs(8) fsck.xfs(8), fsck.xiafs(8) reiserfsck(8).

E2fsprogs version(1,3,5) 1.35           February 2004                         FSCK(8)

References for this manual (incoming links)