Welcome to the Reiser4 Wiki, the Wiki for users and developers of the ReiserFS and Reiser4 filesystems.
For now, most of the documentation is just a snapshot of the old Namesys site (archive.org, 2007-09-29).
There was also a Reiser4 Wiki (archive.org, 2007-07-06) once on pub.namesys.com.
Mkreiserfs
From Reiser4 FS Wiki
(Difference between revisions)
(formatting fixes) |
|||
| Line 1: | Line 1: | ||
| − | mkreiserfs - The | + | mkreiserfs - The tool to create a [[ReiserFS]] filesystem. |
=== SYNOPSIS === | === SYNOPSIS === | ||
| − | + | mkreiserfs [ -dfV ] | |
| − | mkreiserfs [ -dfV ] [ -b | --block-size N ] [ -h | --hash HASH ] [ -u | --uuid UUID ] [ -l | --label LABEL ] [ --format FORMAT ] [ -q | --quiet ] [ -j | --journal-device FILE ] [ -s | --journal-size N ] [ -o | --journal-offset N ] [ -t | --transaction-max-size N ] [ -B | --badblocks file ] device [ filesystem-size ] | + | [ -b | --block-size N ] |
| + | [ -h | --hash HASH ] | ||
| + | [ -u | --uuid UUID ] | ||
| + | [ -l | --label LABEL ] | ||
| + | [ --format FORMAT ] | ||
| + | [ -q | --quiet ] | ||
| + | [ -j | --journal-device FILE ] | ||
| + | [ -s | --journal-size N ] | ||
| + | [ -o | --journal-offset N ] | ||
| + | [ -t | --transaction-max-size N ] | ||
| + | [ -B | --badblocks file ] ''device'' [ ''filesystem-size'' ] | ||
=== DESCRIPTION === | === DESCRIPTION === | ||
| − | mkreiserfs creates a | + | <tt>mkreiserfs</tt> creates a ReiserFS filesystem on a device (usually a disk partition). |
| − | device is the special file corresponding to a device or to a partition (e.g /dev/hdXX for an IDE disk partition or /dev/sdXX for a SCSI disk partition). filesystem-size is the size in blocks of the filesystem. If omitted, mkreiserfs will automatically set it. | + | |
| + | ''device'' is the special file corresponding to a device or to a partition (e.g /dev/hdXX for an IDE disk partition or /dev/sdXX for a SCSI disk partition). | ||
| + | |||
| + | ''filesystem-size'' is the size in blocks of the filesystem. If omitted, | ||
| + | <tt>mkreiserfs</tt> will automatically set it. | ||
=== OPTIONS === | === OPTIONS === | ||
| − | + | -b | --block-size N | |
| − | + | N is block size in bytes. It may only be set to a power of 2 within | |
| − | + | the 512-8192 interval. | |
| − | + | ||
| − | + | -h | --hash HASH | |
| − | + | HASH specifies which hash function will sort the names in the directories. | |
| − | + | Choose from r5, rupasov, or tea. r5 is the default one. | |
| − | + | ||
| − | + | --format FORMAT | |
| − | + | FORMAT specifies the format for the new filsystem. Choose format 3.5 | |
| − | + | or 3.6. If none is specified mkreiserfs will create format 3.6 if | |
| − | + | running kernel is 2.4 or higher, and format 3.5 if kernel 2.2 | |
| − | + | is running, and will refuse creation under all other kernels. | |
| − | + | ||
| − | + | -u | --uuid UUID | |
| − | + | Sets the Universally Unique IDentifier of the filesystem to UUID | |
| − | + | (see also [http://manpages.ubuntu.com/manpages/karmic/en/man1/uuidgen.1.html uuidgen(1)]). | |
| − | + | The format of the UUID is a series of hex digits separated by hypthens, | |
| − | + | e.g.: "c1b9d5a2-f162-11cf9ece-0020afc76f16". If the option is skipped, | |
| − | + | mkreiserfs will by default generate a new UUID. | |
| − | + | ||
| − | + | -l | --label LABEL | |
| − | + | Sets the volume label of the filesystem. LABEL can at most be 16 | |
| − | + | characters long; if it is longer than 16 characters, mkreiserfs | |
| − | + | will truncate it. | |
| − | + | ||
| − | + | -q | --quiet | |
| − | + | Sets mkreiserfs to work quietly without producing messages, progress | |
| − | + | or questions. It is useful, but only for use by end users, if you | |
| − | N is the maximum transaction size parameter for the journal. The default, and max possible, value is 1024 blocks. It should be less than half the size of the journal. If specified incorrectly, it will automatically be adjusted. | + | run mkreiserfs in a script. |
| − | + | ||
| − | + | -j | --journal-device FILE | |
| − | + | FILE is the name of the block device on which is to be places the | |
| − | + | filesystem journal. | |
| − | + | ||
| − | + | -o | --journal-offset N | |
| − | + | N is the offset where the journal starts when it is to be on a | |
| − | + | separate device. Default is 0. N has no effect when the journal | |
| + | is to be on the host device. | ||
| + | |||
| + | -s | --journal-size N | ||
| + | N is the size of the journal in blocks. When the journal is to be | ||
| + | on a separate device, its size defaults to the number of blocks that | ||
| + | the device has. When journal is to be on the host device, its size | ||
| + | defaults to 8193 and the maximal possible size is 32749 (for blocksize | ||
| + | 4k). The minimum size is 513 blocks (whether the journal is on the | ||
| + | host or on a separate device). | ||
| + | |||
| + | -t | --transaction-max-size N | ||
| + | N is the maximum transaction size parameter for the journal. The | ||
| + | default, and max possible, value is 1024 blocks. It should be less | ||
| + | than half the size of the journal. If specified incorrectly, it will | ||
| + | automatically be adjusted. | ||
| + | |||
| + | -B | --badblocks file | ||
| + | File is the file name of the file that contains the list of blocks to | ||
| + | be marked as bad on the filesystem. This list can be created by | ||
| + | [[FAQ/bad-block-handling|badblocks]] -b block-size device. | ||
| + | |||
| + | -f Forces mkreiserfs to continue even when the device is | ||
| + | the whole disk, looks mounted, or is not a block device. If -f | ||
| + | is specified more than once, it allows the user to avoid asking | ||
| + | for confirmation. | ||
| + | |||
| + | -d Sets mkreiserfs to print debugging information during mkreiserfs. | ||
| + | |||
| + | -V Prints the version and then exits. | ||
=== AUTHOR === | === AUTHOR === | ||
| − | This version of mkreiserfs has been written by Edward Shishkin <edward@ | + | This version of mkreiserfs has been written by Edward Shishkin <edward.shishkin@gmail.com>. |
=== BUGS === | === BUGS === | ||
| − | Please report bugs to the ReiserFS developers | + | Please [[mailinglists|report bugs to the ReiserFS developers]], providing as much information as possible--your hardware, kernel, patches, settings, all printed messages; check the syslog file for any related information. |
=== SEE ALSO === | === SEE ALSO === | ||
| − | + | * [[reiserfsck|reiserfsck(8)]] | |
| + | * [[debugreiserfs|debugreiserfs(8)]] | ||
| + | * [[reiserfstune|reiserfstune(8)]] | ||
[[category:ReiserFS]] | [[category:ReiserFS]] | ||
Revision as of 20:56, 27 June 2009
mkreiserfs - The tool to create a ReiserFS filesystem.
Contents |
SYNOPSIS
mkreiserfs [ -dfV ]
[ -b | --block-size N ]
[ -h | --hash HASH ]
[ -u | --uuid UUID ]
[ -l | --label LABEL ]
[ --format FORMAT ]
[ -q | --quiet ]
[ -j | --journal-device FILE ]
[ -s | --journal-size N ]
[ -o | --journal-offset N ]
[ -t | --transaction-max-size N ]
[ -B | --badblocks file ] device [ filesystem-size ]
DESCRIPTION
mkreiserfs creates a ReiserFS filesystem on a device (usually a disk partition).
device is the special file corresponding to a device or to a partition (e.g /dev/hdXX for an IDE disk partition or /dev/sdXX for a SCSI disk partition).
filesystem-size is the size in blocks of the filesystem. If omitted, mkreiserfs will automatically set it.
OPTIONS
-b | --block-size N N is block size in bytes. It may only be set to a power of 2 within the 512-8192 interval.
-h | --hash HASH HASH specifies which hash function will sort the names in the directories. Choose from r5, rupasov, or tea. r5 is the default one.
--format FORMAT FORMAT specifies the format for the new filsystem. Choose format 3.5 or 3.6. If none is specified mkreiserfs will create format 3.6 if running kernel is 2.4 or higher, and format 3.5 if kernel 2.2 is running, and will refuse creation under all other kernels.
-u | --uuid UUID Sets the Universally Unique IDentifier of the filesystem to UUID (see also uuidgen(1)). The format of the UUID is a series of hex digits separated by hypthens, e.g.: "c1b9d5a2-f162-11cf9ece-0020afc76f16". If the option is skipped, mkreiserfs will by default generate a new UUID.
-l | --label LABEL Sets the volume label of the filesystem. LABEL can at most be 16 characters long; if it is longer than 16 characters, mkreiserfs will truncate it.
-q | --quiet Sets mkreiserfs to work quietly without producing messages, progress or questions. It is useful, but only for use by end users, if you run mkreiserfs in a script.
-j | --journal-device FILE FILE is the name of the block device on which is to be places the filesystem journal.
-o | --journal-offset N N is the offset where the journal starts when it is to be on a separate device. Default is 0. N has no effect when the journal is to be on the host device.
-s | --journal-size N N is the size of the journal in blocks. When the journal is to be on a separate device, its size defaults to the number of blocks that the device has. When journal is to be on the host device, its size defaults to 8193 and the maximal possible size is 32749 (for blocksize 4k). The minimum size is 513 blocks (whether the journal is on the host or on a separate device).
-t | --transaction-max-size N N is the maximum transaction size parameter for the journal. The default, and max possible, value is 1024 blocks. It should be less than half the size of the journal. If specified incorrectly, it will automatically be adjusted.
-B | --badblocks file File is the file name of the file that contains the list of blocks to be marked as bad on the filesystem. This list can be created by badblocks -b block-size device.
-f Forces mkreiserfs to continue even when the device is the whole disk, looks mounted, or is not a block device. If -f is specified more than once, it allows the user to avoid asking for confirmation.
-d Sets mkreiserfs to print debugging information during mkreiserfs.
-V Prints the version and then exits.
AUTHOR
This version of mkreiserfs has been written by Edward Shishkin <edward.shishkin@gmail.com>.
BUGS
Please report bugs to the ReiserFS developers, providing as much information as possible--your hardware, kernel, patches, settings, all printed messages; check the syslog file for any related information.
