build_e2fs

NAME

SINOPSYS

build_e2fs [ -c|-l filename ] [-b blocksize]
       [-f fragment-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] inode_table device [blocks-count]

DESCRIPTION

Filesystem building consist of several steps:

1) at first in separate bits map marks all blocks in which will be kept filesystem system information.

2) then it frees this blocks from user information.
WARNING. If device has small free space, at this stage possible not shortage space for new filesystem, so not only old filesystem will be destroyed, but new filesystem would not be built. Nevertheless changed inode table will be saved if it's possible. But it will better to avoid so situation by running utility with -n option at first.

3) At last it builds filesystem, writes filesystem system information.
At this stage also may be errors, nevertheless after second stage new inode table already saved and it should not to lead to irrevocable data loss.         
 

OPTIONS

-b blocksize

Filesystem blocksize given in inode table. Trying to point using this option blocksize different with pointed in inode table leads to error message and advice to use reblock(8) for changing filesystem blocksize.

-c

If this option was specified twice, mke2fs used destructive, read-write test for searching of bad blocks, this was changed to NONdestructive read-write test.

-n

causes build_e2fs to not actually build a filesystem, nevertheless so you may to know if there are not enough space for locating new filesystem on device.

-q

Don't print any messages.

-v

you may to point this option to 3 times, with each time more increase quantity of output messages.

-V

Print the version number and exit.

inode_table

external inode table, from which it will read information about locating user data files of current filesystem, its access permissions and directory structure.

device

device for building new filesystem.

USAGE EXAMPLES

Build ext2fs:
$ build_e2fs inode.table /dev/hda1

Check for enough free space on device for ext3fs:
$ build_e2fs -nj inode.table /dev/hda1

Build ext3fs filesystem:
$ build_e2fs -j inode.table /dev/hda1

AUTHOR

BUG REPORTS

You may append to problem description also the inode table (compressed with gzip or bzip2 it must has not so more size) and device/image size.

Block device size in 512 byte blocks you can get with command `/sbin/blockdev --getsize <device>`

AVAILABILITY

SEE ALSO

Index

NAME

SINOPSYS

DESCRIPTION

OPTIONS

USAGE EXAMPLES

AUTHOR

BUG REPORTS

AVAILABILITY

SEE ALSO