Header Ads Widget

[MAN] mkfs

Content-type: text/html; charset=UTF-8 Man page of MKFS.JFFS2

MKFS.JFFS2

Section: User Commands (1)
Index Return to Main Contents
 

NAME

mkfs.jffs2 - Create a JFFS2 file system image from directory  

SYNOPSIS

mkfs.jffs2 [ -p,--pad[=SIZE] ] [ -r,-d,--root directory ] [ -s,--pagesize=SIZE ] [ -e,--eraseblock=SIZE ] [ -c,--cleanmarker=SIZE ] [ -n,--no-cleanmarkers ] [ -o,--output image.jffs2 ] [ -l,--little-endian ] [ -b,--big-endian ] [ -D,--devtable=FILE ] [ -f,--faketime ] [ -q,--squash ] [ -U,--squash-uids ] [ -P,--squash-perms ] [ --with-xattr ] [ --with-selinux ] [ --with-posix-acl ] [ -m,--compression-mode=MODE ] [ -x,--disable-compressor=NAME ] [ -X,--enable-compressor=NAME ] [ -y,--compressor-priority=PRIORITY:NAME ] [ -L,--list-compressors ] [ -t,--test-compression ] [ -h,--help ] [ -v,--verbose ] [ -V,--version ] [ -i,--incremental image.jffs2 ]

 

DESCRIPTION

The program mkfs.jffs2 creates a JFFS2 (Second Journalling Flash File System) file system image and writes the resulting image to the file specified by the -o option or by default to the standard output, unless the standard output is a terminal device in which case mkfs.jffs2 will abort.

The file system image is created using the files and directories contained in the directory specified by the option -r or the present directory, if the -r option is not specified.

Each block of the files to be placed into the file system image are compressed using one of the available compressors depending on the selected compression mode.

File systems are created with the same endianness as the host, unless the -b or -l options are specified. JFFS2 driver in the 2.4 Linux kernel only supported images having the same endianness as the CPU. As of 2.5.48, the kernel can be changed with a #define to accept images of the non-native endianness. Full bi-endian support in the kernel is not planned.

It is unlikely that JFFS2 images are useful except in conjuction with the MTD (Memory Technology Device) drivers in the Linux kernel, since the JFFS2 file system driver in the kernel requires MTD devices.  

OPTIONS

Options that take SIZE arguments can be specified as either decimal (e.g., 65536), octal (0200000), or hexidecimal (0x1000).
-p, --pad[=SIZE]
Pad output to SIZE bytes with 0xFF. If SIZE is not specified, the output is padded to the end of the final erase block.
-r, -d, --root=DIR
Build file system from directory DIR. The default is the current directory.
-s, --pagesize=SIZE
Use page size SIZE. The default is 4 KiB. This size is the maximum size of a data node. Set according to target system's memory management page size (NOTE: this is NOT related to NAND page size).
-e, --eraseblock=SIZE
Use erase block size SIZE. The default is 64 KiB. If you use a erase block size different than the erase block size of the target MTD device, JFFS2 may not perform optimally. If the SIZE specified is below 4096, the units are assumed to be KiB.
-c, --cleanmarker=SIZE
Write 'CLEANMARKER' nodes with the size specified. It is not normally appropriate to specify a size other than the default 12 bytes.
-n, --no-cleanmarkers
Do not write 'CLEANMARKER' nodes to the beginning of each erase block. This option can be useful for creating JFFS2 images for use on NAND flash, and for creating images which are to be used on a variety of hardware with differing eraseblock sizes.
-o, --output=FILE
Write JFFS2 image to file FILE. Default is the standard output.
-l, --little-endian
Create a little-endian JFFS2 image. Default is to make an image with the same endianness as the host.
-b, --big-endian
Create a big-endian JFFS2 image. Default is to make an image with the same endianness as the host.
-D, --devtable=FILE
Use the named FILE as a device table file, for including devices and changing permissions in the created image when the user does not have appropriate permissions to create them on the file system used as source.
-f, --faketime
Change all file timestamps to '0' for regression testing.
-q, --squash
Squash permissions and owners, making all files be owned by root and removing write permission for 'group' and 'other'.
-U, --squash-uids
Squash owners making all files be owned by root.
-P, --squash-perms
Squash permissions, removing write permission for 'group' and 'other'.
--with-xattr
Enables xattr, stuff all xattr entries into jffs2 image file.
--with-selinux
Enables xattr, stuff only SELinux Labels into jffs2 image file.
--with-posix-acl
Enable xattr, stuff only POSIX ACL entries into jffs2 image file.
-m, --compression-mode=MODE
Set the default compression mode. The default mode is priority which tries the compressors in a predefinied order and chooses the first successful one. The alternatives are: none (mkfs will not compress) and size (mkfs will try all compressor and chooses the one which have the smallest result).
-x, --disable-compressor=NAME
Disable a compressor. Use -L to see the list of the available compressors and their default states.
-X, --enable-compressor=NAME
Enable a compressor. Use -L to see the list of the available compressors and their default states.
-y, --compressor-priority=PRIORITY:NAME
Set the priority of a compressor. Use -L to see the list of the available compressors and their default priority. Priorities are used by priority compression mode.
-L, --list-compressors
Show the list of the available compressors and their states.
-t, --test-compression
Call decompress after every compress - and compare the result with the original data -, and some other check.
-h, --help
Display help text.
-v, --verbose
Verbose operation.
-V, --version
Display version information.
-i, --incremental=FILE
Generate an appendage image for FILE. If FILE is written to flash and flash is appended with the output, then it seems as if it was one thing.

 

LIMITATIONS

The format and grammar of the device table file does not allow it to create symbolic links when the symbolic links are not already present in the root working directory.

However, symbolic links may be specified in the device table file using the l type for the purposes of setting their permissions and ownership.  

BUGS

JFFS2 limits device major and minor numbers to 8 bits each. Some consider this a bug.

mkfs.jffs2 does not properly handle hard links in the input directory structure. Currently, hard linked files will be expanded to multiple identical files in the output image.  

AUTHORS

David Woodhouse
Manual page written by David Schleef <ds@schleef.org>  

SEE ALSO

mkfs(8), mkfs.jffs(1), fakeroot(1)


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
LIMITATIONS
BUGS
AUTHORS
SEE ALSO

This document was created by man2html, using the manual pages.
Time: 04:45:26 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8 Man page of MKFS.BFS

MKFS.BFS

Section: System Administration (8)
Updated: July 2011
Index Return to Main Contents
 

NAME

mkfs.bfs - make an SCO bfs filesystem  

SYNOPSIS

mkfs.bfs [options] device [block-count]  

DESCRIPTION

mkfs.bfs creates an SCO bfs filesystem on a block device (usually a disk partition or a file accessed via the loop device).

The block-count parameter is the desired size of the filesystem, in blocks. If nothing is specified, the entire partition will be used.  

OPTIONS

-N, --inodes number
Specify the desired number of inodes (at most 512). If nothing is specified, some default number in the range 48-512 is picked depending on the size of the partition.
-V, --vname label
Specify the volume label. I have no idea if/where this is used.
-F, --fname name
Specify the filesystem name. I have no idea if/where this is used.
-v, --verbose
Explain what is being done.
-c
This option is silently ignored.
-l
This option is silently ignored.
-h, --help
Display help text and exit.
-V, --version
Display version information and exit. Option -V only works as --version when it is the only option.
 

EXIT CODES

The exit code returned by mkfs.bfs is 0 when all went well, and 1 when something went wrong.  

SEE ALSO

mkfs(8)  

AVAILABILITY

The mkfs.bfs command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXIT CODES
SEE ALSO
AVAILABILITY

This document was created by man2html, using the manual pages.
Time: 04:46:00 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8 Man page of MKFS

MKFS

Section: System Administration (8)
Updated: June 2011
Index Return to Main Contents
 

NAME

mkfs - build a Linux filesystem  

SYNOPSIS

mkfs [options] [-t type] [fs-options] device [size]  

DESCRIPTION

This mkfs frontend is deprecated in favour of filesystem specific mkfs.<type> utils.

mkfs is used to build a Linux filesystem on a device, usually a hard disk partition. The device argument is either the device name (e.g. /dev/hda1, /dev/sdb2), or a regular file that shall contain the filesystem. The size argument is the number of blocks to be used for the filesystem.

The exit code returned by mkfs is 0 on success and 1 on failure.

In actuality, mkfs is simply a front-end for the various filesystem builders (mkfs.fstype) available under Linux. The filesystem-specific builder is searched for via your PATH environment setting only. Please see the filesystem-specific builder manual pages for further details.  

OPTIONS

-t, --type type
Specify the type of filesystem to be built. If not specified, the default filesystem type (currently ext2) is used.
fs-options
Filesystem-specific options to be passed to the real filesystem builder.
-V, --verbose
Produce verbose output, including all filesystem-specific commands that are executed. Specifying this option more than once inhibits execution of any filesystem-specific commands. This is really only useful for testing.
-V, --version
Display version information and exit. (Option -V will display version information only when it is the only parameter, otherwise it will work as --verbose.)
-h, --help
Display help text and exit.
 

BUGS

All generic options must precede and not be combined with filesystem-specific options. Some filesystem-specific programs do not automatically detect the device size and require the size parameter to be specified.  

AUTHORS

David Engel (david@ods.com)
Fred N. van Kempen (waltje@uwalt.nl.mugnet.org)
Ron Sommeling (sommel@sci.kun.nl)
The manual page was shamelessly adapted from Remy Card's version for the ext2 filesystem.  

SEE ALSO

fs(5), badblocks(8), fsck(8), mkdosfs(8), mke2fs(8), mkfs.bfs(8), mkfs.ext2(8), mkfs.ext3(8), mkfs.ext4(8), mkfs.minix(8), mkfs.msdos(8), mkfs.vfat(8), mkfs.xfs(8)  

AVAILABILITY

The mkfs command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
BUGS
AUTHORS
SEE ALSO
AVAILABILITY

This document was created by man2html, using the manual pages.
Time: 04:46:01 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8 Man page of MKFS.FAT

MKFS.FAT

Section: Maintenance Commands (8)
Updated: 2016-01-25
Index Return to Main Contents
 

NAME

mkfs.fat - create an MS-DOS filesystem under Linux  

SYNOPSIS

mkfs.fat [OPTIONS] DEVICE [BLOCK-COUNT]  

DESCRIPTION

mkfs.fat is used to create an MS-DOS filesystem under Linux on a device (usually a disk partition). DEVICE is the special file corresponding to the device (e.g. /dev/sdXX). BLOCK-COUNT is the number of blocks on the device. If omitted, mkfs.fat automatically determines the filesystem size.  

OPTIONS

-a
Normally, for any filesystem except very small ones, mkfs.fat will align all the data structures to cluster size, to make sure that as long as the partition is properly aligned, so will all the data structures in the filesystem. This option disables alignment; this may provide a handful of additional clusters of storage at the expense of a significant performance degradation on RAIDs, flash media or large-sector hard disks.
-A
Use Atari variation of the MS-DOS filesystem. This is default if mkfs.fat is run on an Atari, then this option turns off Atari format. There are some differences when using Atari format: If not directed otherwise by the user, mkfs.fat will always use 2 sectors per cluster, since GEMDOS doesn't like other values very much. It will also obey the maximum number of sectors GEMDOS can handle. Larger filesystems are managed by raising the logical sector size. Under Atari format, an Atari-compatible serial number for the filesystem is generated, and a 12 bit FAT is used only for filesystems that have one of the usual floppy sizes (720k, 1.2M, 1.44M, 2.88M), a 16 bit FAT otherwise. This can be overridden with the -F option. Some PC-specific boot sector fields aren't written, and a boot message (option -m) is ignored.
-b SECTOR-OF-BACKUP
Selects the location of the backup boot sector for FAT32. Default depends on number of reserved sectors, but usually is sector 6. The backup must be within the range of reserved sectors.
-c
Check the device for bad blocks before creating the filesystem.
-C
Create the file given as DEVICE on the command line, and write the to-be-created filesystem to it. This can be used to create the new filesystem in a file instead of on a real device, and to avoid using dd in advance to create a file of appropriate size. With this option, the BLOCK-COUNT must be given, because otherwise the intended size of the filesystem wouldn't be known. The file created is a sparse file, which actually only contains the meta-data areas (boot sector, FATs, and root directory). The data portions won't be stored on the disk, but the file nevertheless will have the correct size. The resulting file can be copied later to a floppy disk or other device, or mounted through a loop device.
-D DRIVE-NUMBER
Specify the BIOS drive number to be stored in the FAT boot sector. This value is usually 0x80 for hard disks and 0x00 for floppy devices or partitions to be used for floppy emulation.
-f NUMBER-OF-FATS
Specify the number of file allocation tables in the filesystem. The default is 2.
-F FAT-SIZE
Specifies the type of file allocation tables used (12, 16 or 32 bit). If nothing is specified, mkfs.fat will automatically select between 12, 16 and 32 bit, whatever fits better for the filesystem size.
-h NUMBER-OF-HIDDEN-SECTORS
Select the number of hidden sectors in the volume. Apparently some digital cameras get indigestion if you feed them a CF card without such hidden sectors, this option allows you to satisfy them.
-i VOLUME-ID
Sets the volume ID of the newly created filesystem; VOLUME-ID is a 32-bit hexadecimal number (for example, 2e24ec82). The default is a number which depends on the filesystem creation time.
-I
It is typical for fixed disk devices to be partitioned so, by default, you are not permitted to create a filesystem across the entire device. mkfs.fat will complain and tell you that it refuses to work. This is different when using MO disks. One doesn't always need partitions on MO disks. The filesystem can go directly to the whole disk. Under other OSes this is known as the 'superfloppy' format. This switch will force mkfs.fat to work properly.
-l FILENAME
Read the bad blocks list from FILENAME.
-m MESSAGE-FILE
Sets the message the user receives on attempts to boot this filesystem without having properly installed an operating system. The message file must not exceed 418 bytes once line feeds have been converted to carriage return-line feed combinations, and tabs have been expanded. If the filename is a hyphen (-), the text is taken from standard input.
-M FAT-MEDIA-TYPE
Specify the media type to be stored in the FAT boot sector. This value is usually 0xF8 for hard disks and is 0xF0 or a value from 0xF9 to 0xFF for floppies or partitions to be used for floppy emulation.
-n VOLUME-NAME
Sets the volume name (label) of the filesystem. The volume name can be up to 11 characters long. The default is no label.
-r ROOT-DIR-ENTRIES
Select the number of entries available in the root directory. The default is 112 or 224 for floppies and 512 for hard disks.
-R NUMBER-OF-RESERVED-SECTORS
Select the number of reserved sectors. With FAT32 format at least 2 reserved sectors are needed, the default is 32. Otherwise the default is 1 (only the boot sector).
-s SECTORS-PER-CLUSTER
Specify the number of disk sectors per cluster. Must be a power of 2, i.e. 1, 2, 4, 8, ... 128.
-S LOGICAL-SECTOR-SIZE
Specify the number of bytes per logical sector. Must be a power of 2 and greater than or equal to 512, i.e. 512, 1024, 2048, 4096, 8192, 16384, or 32768. Values larger than 4096 are not conforming to the FAT file system specification and may not work everywhere.
-v
Verbose execution.
--invariant
Use constants for normally randomly generated or time based data such as volume ID and creation time. Multiple runs of mkfs.fat on the same device create identical results with this option. Its main purpose is testing mkfs.fat.
--help
Display option summary and exit.
 

BUGS

mkfs.fat can not create boot-able filesystems. This isn't as easy as you might think at first glance for various reasons and has been discussed a lot already. mkfs.fat simply will not support it ;)  

SEE ALSO

fatlabel(8)
fsck.fat(8)  

HOMEPAGE

The home for the dosfstools project is its GitHub project page  

AUTHORS

dosfstools were written by Werner Almesberger Roman Hodek and others. The current maintainer is Andreas Bombe


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
BUGS
SEE ALSO
HOMEPAGE
AUTHORS

This document was created by man2html, using the manual pages.
Time: 04:46:01 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8 Man page of MKFS.CRAMFS

MKFS.CRAMFS

Section: System Administration (8)
Updated: April 2013
Index Return to Main Contents
 

NAME

mkfs.cramfs - make compressed ROM file system  

SYNOPSIS

mkfs.cramfs [options] directory file  

DESCRIPTION

Files on cramfs file systems are zlib-compressed one page at a time to allow random read access. The metadata is not compressed, but is expressed in a terse representation that is more space-efficient than conventional file systems.

The file system is intentionally read-only to simplify its design; random write access for compressed files is difficult to implement. cramfs ships with a utility (mkcramfs) to pack files into new cramfs images.

File sizes are limited to less than 16 MB.

Maximum file system size is a little under 272 MB. (The last file on the file system must begin before the 256 MB block, but can extend past it.)  

ARGUMENTS

The directory is simply the root of the directory tree that we want to generate a compressed filesystem out of.

The file will contain the cram file system, which later can be mounted.  

OPTIONS

-v
Enable verbose messaging.
-E
Treat all warnings as errors, which are reflected as command return value.
-b blocksize
Use defined block size, which has to be divisible by page size.
-e edition
Use defined file system edition number in superblock.
-N big, little, host
Use defined endianness. Value defaults to host.
-i file
Insert a file to cramfs file system.
-n name
Set name of the cramfs file system.
-p
Pad by 512 bytes for boot code.
-s
This option is ignored. Originally the -s turned on directory entry sorting.
-z
Make explicit holes.
-h, --help
Display help text and exit.
-V, --version
Display version information and exit.
 

EXIT STATUS

0
success
8
operation error, such as unable to allocate memory
 

SEE ALSO

fsck.cramfs(8), mount(8)  

AVAILABILITY

The example command is part of the util-linux package and is available from Linux Kernel Archive


 

Index

NAME
SYNOPSIS
DESCRIPTION
ARGUMENTS
OPTIONS
EXIT STATUS
SEE ALSO
AVAILABILITY

This document was created by man2html, using the manual pages.
Time: 04:46:02 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8 Man page of MKFS.MINIX

MKFS.MINIX

Section: System Administration (8)
Updated: June 2015
Index Return to Main Contents
 

NAME

mkfs.minix - make a Minix filesystem  

SYNOPSIS

mkfs.minix [options] device [size-in-blocks]  

DESCRIPTION

mkfs.minix creates a Linux MINIX filesystem on a device (usually a disk partition).

The device is usually of the following form:

/dev/hda[1-8] (IDE disk 1) /dev/hdb[1-8] (IDE disk 2) /dev/sda[1-8] (SCSI disk 1) /dev/sdb[1-8] (SCSI disk 2)

The device may be a block device or a image file of one, but this is not enforced. Expect not much fun on a character device :-).

The size-in-blocks parameter is the desired size of the file system, in blocks. It is present only for backwards compatibility. If omitted the size will be determined automatically. Only block counts strictly greater than 10 and strictly less than 65536 are allowed.  

OPTIONS

-c, --check
Check the device for bad blocks before creating the filesystem. If any are found, the count is printed.
-n, --namelength length
Specify the maximum length of filenames. Currently, the only allowable values are 14 and 30 for file system versions 1 and 2. Version 3 allows only value 60. The default is 30.
-i, --inodes number
Specify the number of inodes for the filesystem.
-l, --badblocks filename
Read the list of bad blocks from filename. The file has one bad-block number per line. The count of bad blocks read is printed.
-1
Make a Minix version 1 filesystem. This is the default.
-2, -v
Make a Minix version 2 filesystem.
-3
Make a Minix version 3 filesystem.
-V, --version
Display version information and exit. The long option cannot be combined with other options.
-h, --help
Display help text and exit.
 

EXIT CODES

The exit code returned by mkfs.minix is one of the following:
0
No errors
8
Operational error
16
Usage or syntax error
 

SEE ALSO

fsck(8), mkfs(8), reboot(8)  

AVAILABILITY

The mkfs.minix command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXIT CODES
SEE ALSO
AVAILABILITY

This document was created by man2html, using the manual pages.
Time: 04:46:02 GMT, September 16, 2022

댓글 쓰기

0 댓글