Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Bread for the World

 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, 270 guest(s) and 3 member(s) that are online.

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

  

mke2fs



SYNOPSIS

       mke2fs  [  -c | -l filename ] [ -b block-size ] [ -f frag­
       ment-size ] [ -g blocks-per-group ] [ -i bytes-per-inode ]
       [ -j ] [ -J journal-options ] [ -N number-of-inodes ] [ -n
       ] [ -m reserved-blocks-percentage ] [ -o creator-os ] [ -O
       feature[,...]   ]  [  -q  ]  [ -r fs-revision-level ] [ -R
       raid-options ] [ -v ] [ -F ] [  -L  volume-label  ]  [  -M
       last-mounted-directory  ]  [ -S ] [ -T filesystem-type ] [
       -V ] device [ blocks-count ]

       mke2fs -O journal_dev [ -b block-size ] [ -L  volume-label
       ] [ -n ] [ -q ] [ -v ] external-journal [ blocks-count ]


DESCRIPTION

       mke2fs  is used to create an ext2/ext3 filesystem (usually
       in a disk partition).  device is the special  file  corre­
       sponding  to  the device (e.g /dev/hdXX).  blocks-count is
       the number of blocks on the device.   If  omitted,  mke2fs
       automagically  figures the file system size.  If called as
       mkfs.ext3 a journal is created as if  the  -j  option  was
       specified.


OPTIONS

       -b block-size
              Specify  the  size of blocks in bytes.  Valid block
              size vales are 1024, 2048 and 4096 bytes per block.
              If  omitted,  mke2fs  block-size  is  hueristically
              determined by the file system size and the expected
              usage  of  the  filesystem (see the -T option).  If
              block-size  is  negative,  then  mke2fs  will   use
              hueristics to determine the appropriate block size,
              with the constraint that the block size will be  at
              least block-size bytes.  This is useful for certain
              hardware devices which require that  the  blocksize
              be a multiple of 2k.

       -c     Check the device for bad blocks before creating the
              file system.  If this option  is  specified  twice,
              then a slower, destructive, read-write test is used
              instead of a fast read-only test.

       -f fragment-size
              Specify the size of fragments in bytes.

       -F     Force mke2fs to run, even if the  specified  device
              is  not  a  block  special device, or appears to be
              mounted.

       -g blocks-per-group
              Specify the number of  blocks  in  a  block  group.
              There  is  generally no reason the user to ever set
              this parameter, as the default is optimal  for  the
              made.  Be warned that is not possible to expand the
              number  of  inodes on a filesystem after it is cre­
              ated, so be careful deciding the correct value  for
              this parameter.

       -j     Create the filesystem with an ext3 journal.  If the
              -J option is not  specified,  the  default  journal
              parameters  will be used to create an appropriately
              sized journal (given the size  of  the  filesystem)
              stored  within  the filesystem.  Note that you must
              be using a kernel which has ext3 support  in  order
              to actually make use of the journal.

       -J journal-options
              Create  the ext3 journal using options specified on
              the command-line.  Journal options are comma  sepa­
              rated,  and  may  take an argument using the equals
              ('=')  sign.  The  following  journal  options  are
              supported:

                   size=journal-size
                          Create   an   internal  journal  (i.e.,
                          stored inside the filesystem)  of  size
                          journal-size  megabytes.   The  size of
                          the  journal  must  be  at  least  1024
                          filesystem  blocks  (i.e., 1MB if using
                          1k blocks,  4MB  if  using  4k  blocks,
                          etc.)   and may be no more than 102,400
                          filesystem blocks.

                   device=external-journal
                          Attach the filesystem  to  the  journal
                          block  device located on external-jour­
                          nal.  The external journal must already
                          have been created using the command

                          mke2fs -O journal_dev external-journal

                          Note  that  external-journal  must have
                          been created with the same  block  size
                          as the new filesystem.

                          Instead  of  specifying  a  device name
                          directly, external-journal can also  be
                          specified   by  either  LABEL=label  or
                          UUID=UUID to locate the external  jour­
                          nal  by either the volume label or UUID
                          stored in the ext2  superblock  at  the
                          start  of the journal.  Use dumpe2fs(8)
                          to display a  journal  device's  volume
                          label and UUID.  See also the -L option
                          of tune2fs(8).

       -L     Set the volume label for the filesystem.

       -m reserved-blocks-percentage
              Specify the percentage  of  the  filesystem  blocks
              reserved  for  the super-user.  This value defaults
              to 5%.

       -M     Set the last mounted directory for the  filesystem.
              This might be useful for the sake of utilities that
              key off of the last mounted directory to  determine
              where the filesytem should be mounted.

       -n     causes  mke2fs to not actually create a filesystem,
              but display what it would do if it were to create a
              filesystem.   This  can  be  used  to determine the
              location of the backup superblocks for a particular
              filesystem,  so  long as the mke2fs parameters that
              were passed when the filesystem was originally cre­
              ated are used again.  (With the -n option added, of
              course!)

       -N number-of-inodes
              overrides the default calculation of the number  of
              inodes  that  should be reserved for the filesystem
              (which is based on the number  of  blocks  and  the
              bytes-per-inode  ratio).   This  allows the user to
              specify the number of desired inodes directly.

       -o creator-os
              Manually override the default value of the "creator
              os"  field of the filesystem.  Normally the creator
              field is set by default to the  native  OS  of  the
              mke2fs executable.

       -O feature[,...]
              Create  filesystem  with given features (filesystem
              options).  Features which are normally turned on by
              default  may  be  disabled by prefixing the feature
              with  a  caret  ('^')   symbol.    Currently,   the
              sparse_super and filetype features are turned on by
              default when mke2fs is run on a system  with  Linux
              2.2  or  later  (unless  creator-os  is  set to the
              Hurd).  Filesystems that may need to be mounted  on
              pre-2.2  Linux  or  other kernels should be created
              with -O none (or -r 0 for  Linux  1.2)  which  will
              disable  these features, even if mke2fs is run on a
              system which can support them.

              The following filesystem options are supported:

                   dir_index
                          Use hashed b-trees to speed up  lookups
                          must be created  with  the  same  block
                          size  as  the  filesystems that will be
                          using it.

                   sparse_super
                          Create   a   filesystem   with    fewer
                          superblock  backup  copies (saves space
                          on large filesystems).

       -q     Quiet execution.  Useful if  mke2fs  is  run  in  a
              script.

       -r revision
              Set the filesystem revision for the new filesystem.
              Note that  1.2  kernels  only  support  revision  0
              filesystems.   The  default is to create revision 1
              filesystems.

       -R raid-options
              Set raid-related options for the filesystem.   Raid
              options  are comma separated, and may take an argu­
              ment using the equals ('=')  sign.   The  following
              options are supported:

                   stride=stripe-size
                          Configure  the  filesystem  for  a RAID
                          array   with   stripe-size   filesystem
                          blocks per stripe.

       -S     Write  superblock and group descriptors only.  This
              is useful if  all  of  the  superblock  and  backup
              superblocks  are corrupted, and a last-ditch recov­
              ery method is desired.  It causes mke2fs to  reini­
              tialize the superblock and group descriptors, while
              not touching the inode  table  and  the  block  and
              inode  bitmaps.   The  e2fsck program should be run
              immediately after this option is used, and there is
              no guarantee that any data will be salvageable.  It
              is  critical  to  specify  the  correct  filesystem
              blocksize  when  using  this option, or there is no
              chance of recovery.

       -T fs-type
              Specify how the filesystem is going to be used,  so
              that mke2fs can chose optimal filesystem parameters
              for that use.  The supported filesystem types are:

                   news        one inode per 4kb block

                   largefile   one inode per megabyte

                   largefile4  one inode per 4 megabytes

       author.


AVAILABILITY

       mke2fs is part of the e2fsprogs package and  is  available
       from http://e2fsprogs.sourceforge.net.


SEE ALSO

       badblocks(8), dumpe2fs(8), e2fsck(8), tune2fs(8)

E2fsprogs version 1.34      July 2003                   MKE2FS(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 choose larger fonts by selecting a different themes.


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