Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
HP & Linux

 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

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

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

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

  

fsck.ext2



SYNOPSIS

       e2fsck  [ -pacnyrdfvstDFSV ] [ -b superblock ] [ -B block­
       size ] [ -l|-L bad_blocks_file ] [ -C fd ] [ -j  external-
       journal ] [ -E extended_options ] device


DESCRIPTION

       e2fsck  is used to check a Linux second extended file sys­
       tem (ext2fs).  E2fsck also supports ext2 filesystems coun­
       taining  a journal, which are also sometimes known as ext3
       filesystems, by first applying the journal to the filesys­
       tem  before  continuing  with  normal  e2fsck  processing.
       After the journal has been applied, a filesystem will nor­
       mally  be  marked  as clean.  Hence, for ext3 filesystems,
       e2fsck will normally run the journal and exit, unless  its
       superblock indicates that further checking is required.

       device  is  the device file where the filesystem is stored
       (e.g.  /dev/hdc1).


OPTIONS

       -a     This option does the same thing as the  -p  option.
              It is provided for backwards compatibility only; it
              is suggested that people  use  -p  option  whenever
              possible.

       -b superblock
              Instead  of  using  the  normal  superblock, use an
              alternative  superblock  specified  by  superblock.
              This  option  is  normally  used  when  the primary
              superblock has been corrupted.  The location of the
              backup  superblock is dependent on the filesystem's
              blocksize.  For filesystems with 1k  blocksizes,  a
              backup  superblock  can be found at block 8193; for
              filesystems with 2k blocksizes, at block 16384; and
              for 4k blocksizes, at block 32768.

              Additional  backup superblocks can be determined by
              using the mke2fs program using  the  -n  option  to
              print out where the superblocks were created.   The
              -b option to mke2fs, which specifies  blocksize  of
              the  filesystem  must be specified in order for the
              superblock locations that are  printed  out  to  be
              accurate.

              If  an  alternative superblock is specified and the
              filesystem is not  opened  read-only,  e2fsck  will
              make  sure  that  the primary superblock is updated
              appropriately upon  completion  of  the  filesystem
              check.

       -B blocksize
              Normally,  e2fsck will search for the superblock at

       -C fd  This  option  causes  e2fsck  to  write  completion
              information  to  the  specified  file descriptor so
              that the progress of the filesystem  check  can  be
              monitored.   This  option is typically used by pro­
              grams  which  are  running  e2fsck.   If  the  file
              descriptor specified is 0, e2fsck will print a com­
              pletion bar as it goes about  its  business.   This
              requires  that e2fsck is running on a video console
              or terminal.

       -d     Print debugging  output  (useless  unless  you  are
              debugging e2fsck).

       -D     Optimize  directories  in  filesystem.  This option
              causes e2fsck to try to optimize  all  directories,
              either  by  reindexing  them if the filesystem sup­
              ports directory indexing,  or by sorting  and  com­
              pressing  directories  for  smaller directories, or
              for filesystems using traditional  linear  directo­
              ries.

       -E extended_options
              Set  e2fsck extended options.  Extended options are
              comma separated, and may take an argument using the
              equals  ('=') sign.  The following options are sup­
              ported:

                   ea_ver=extended_attribute_version
                          Assume  the  format  of  the   extended
                          attribute  blocks  in the filesystem is
                          the specified version number.  The ver­
                          sion number may be 1 or 2.  The default
                          extended attribute version format is 2.

       -f     Force checking even if the file system seems clean.

       -F     Flush the filesystem device's buffer caches  before
              beginning.   Only  really  useful  for doing e2fsck
              time trials.

       -j external-journal
              Set the pathname  where  the  external-journal  for
              this filesystem can be found.

       -l filename
              Add  the block numbers listed in the file specified
              by filename to the list of bad blocks.  The  format
              of  this  file  is the same as the one generated by
              the badblocks(8) program.  Note that the block num­
              bers  are based on the blocksize of the filesystem.
              Hence, badblocks(8) must be given the blocksize  of
              the  filesystem in order to obtain correct results.
              non-interactively.   (Note:  if  the  -c, -l, or -L
              options are specified in addition to the -n option,
              then  the  filesystem will be opened read-write, to
              permit the bad-blocks list to be updated.  However,
              no other changes will be made to the filesystem.)

       -p     Automatically  repair  ("preen")  the  file  system
              without any questions.

       -r     This option does nothing at  all;  it  is  provided
              only for backwards compatibility.

       -s     This  option  will byte-swap the filesystem so that
              it is using  the  normalized,  standard  byte-order
              (which  is i386 or little endian).  If the filesys­
              tem is already in the standard  byte-order,  e2fsck
              will take no action.

       -S     This  option will byte-swap the filesystem, regard­
              less of its current byte-order.

       -t     Print timing statistics for e2fsck.  If this option
              is  used  twice,  additional  timing statistics are
              printed on a pass by pass basis.

       -v     Verbose mode.

       -V     Print version information and exit.

       -y     Assume an answer of `yes' to all questions;  allows
              e2fsck to be used non-interactively.


EXIT CODE

       The exit code returned by e2fsck is the sum of the follow­
       ing conditions:
            0    - No errors
            1    - File system errors corrected
            2    - File system errors corrected, system should
                   be rebooted
            4    - File system errors left uncorrected
            8    - Operational error
            16   - Usage or syntax error
            32   - E2fsck canceled by user request
            128  - Shared library error


SIGNALS

       The following signals have the following effect when  sent
       to e2fsck.

       SIGUSR1
              This  signal  causes  e2fsck  to start displaying a
              completion bar.  (See discussion of the -C option.)

       displayed.  If you have a writeable filesystem  where  the
       transcript can be stored, the script(1) program is a handy
       way to save the output of e2fsck to a file.

       It is also useful to send the output of dumpe2fs(8).  If a
       specific  inode  or inodes seems to be giving e2fsck trou­
       ble, try running the debugfs(8) command and send the  out­
       put  of the stat(1u) command run on the relevant inode(s).
       If the inode is a directory, the debugfs dump command will
       allow  you to extract the contents of the directory inode,
       which can sent to me after being first run  through  uuen­
       code(1).

       Always  include  the full version string which e2fsck dis­
       plays when it is run, so I know which version you are run­
       ning.


AUTHOR

       This  version  of  e2fsck  was  written  by  Theodore Ts'o
       <tytso@mit.edu>.


SEE ALSO

       mke2fs(8), tune2fs(8), dumpe2fs(8), debugfs(8)

E2fsprogs version 1.34      July 2003                   E2FSCK(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.


Login
Nickname

Password

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?
You can help in many different ways.


Friends



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.09 Seconds