mkfs(1M-vxfs) (VxFS) mkfs(1M-vxfs)
NAME
mkfs (vxfs) - construct a Veritas File System (VxFS)
SYNOPSIS
mkfs [-F vxfs] [genericoptions] [-o specificoptions] special size
DESCRIPTION
mkfs constructs a file system by writing to the special file special
unless the -o N flag has been specified. The numeric size specifies
the number of sectors in the file system. If size is given as - (a
dash), then the entire device size will be used. mkfs builds a file
system with a root directory and a lost+found directory [see
fsck(1M)]. The number of inodes is calculated as a function of the
file system size. No boot program is initialized by mkfs.
genericoptions indicate options that are supported by the generic
mkfs(1M) command. specificoptions indicate suboptions that are sup-
ported only by the Veritas-specific module of the mkfs command. They
are specified in a comma-separated list and/or as keyword-attribute
pairs. These suboptions are specified via the -o option.
OPTIONS
-F vxfs Specifies the Veritas file system type (FSType).
genericoptions
Options supported by the generic mkfs command.
-o Specifies the Veritas file system specific options in a
comma-separated list. The following options are available:
N The file system is not written to the special
file. This option gives all the information
needed to create a file system but does not
create it.
ninode=n n is the number of inodes on the file system,
rounded down. The default is the total number of
blocks in allocation units divided by four.
nau=n n is the number of allocation units on the file
system. The default is the number of available
blocks, after the super block and log area have
been allocated, divided by 32768. Each alloca-
tion unit will have an equal number of blocks of
size bsize. This may result in the size of the
resulting file system being smaller than that
specified by size.
Page 1 Reliant UNIX 5.44 Printed 11/98
mkfs(1M-vxfs) (VxFS) mkfs(1M-vxfs)
bsize=n n is the block size for files on the file system
and represents the smallest amount of disk space
that will be allocated to a file. n must be a
power of two currently selected from the range
1024 to 8192. The default is 1024, or the sector
size, whichever is larger. In the case of file
systems >32 GB, the block size depends on the
maximum file size (see maxfilesize option) as
well as on the size of the device file (it must
be possible to display the block numbers in a
"signed 32-bit-long").
logsize=n n is the number of blocks to allocate for an
activity logging area. n must be in the range of
32 to 32768. The default is 256.
maxfilesize=n
n is the maximum size of a file in the file sys-
tem to be created (unit: gigabyte).
n must be a power of two in the range 32 to
16384. By default, maxfilesize is at least as
large as the file system.
Note: If the maximum file size is less than the
size of the file system, it is not possible for
a file to be larger than the maxfilesize, even
if there is enough disk space available (see the
notes at the end of this manual page).
iaddrlen=n n is the size of the indirect address extents
for setting up the indirect levels (see "VxFS
System Administrator's Guide") (unit: blocks). n
must be a power of two in the range 1 to 64.
iaddrlen * bsize must be >= 8 KB and =< 64 KB
(see also the notes at the end of this manual
page).
indsize=n n is the size of the indirect extents in the
indirect levels (see "VxFS System Administra-
tor's Guide") (unit: blocks). n must be a power
of two in the range 1 to 1024.
indsize * bsize must be >= 8 KB (see also the
notes at the end of this manual page).
ausize=n n is the size in bsize blocks of size of an
allocation unit. This is an alternate way of
specifying the number of allocations units. This
option may not be used in conjunction with the
nau option. With this option, the last
Page 2 Reliant UNIX 5.44 Printed 11/98
mkfs(1M-vxfs) (VxFS) mkfs(1M-vxfs)
allocation unit on the file system may be
shorter than the others. If the last allocation
unit on the file system is not long enough to
contain an entire allocation unit header, the
resulting size of the file system will be to the
end of the last complete allocation unit.
aufirst=n n is the starting block number in bsize blocks
of size of the first allocation unit. This
option allows the allocation units to be aligned
to a particular boundary, such as a cylinder
boundary.
aupad=n The size in bsize blocks of size to leave
between the end of the inode list and the first
data block in each allocation unit. This option
allows the data blocks of an allocation unit to
be aligned to a particular boundary, such as a
cylinder boundary.
NOTES
The following tables show the relationship between bsize, iaddrlen and
indsize with regard to maxfilesize. If iaddrlen and indsize are not
specified, mkfs uses the following strategy to represent the maximum
file size:
iaddrlen is increased first: If it is not sufficient for maxfilesize,
indsize is then increased and iaddrlen is set to the lowest possible
value. This procedure reduces the space requirement for managing the
data in the indirect levels.
The maximum file sizes for different iaddrlen values and a bsize value
of 1 KB:
______________________________________________________________________
| bsize 1 KB| indsize (blocks) |
| | |
| iaddrlen | 8 16 32 64 128 256 512 1024|
| (blocks) | |
|||
| | |
| 8 | 32GB 64GB 128GB 256GB 512GB 1TB 2TB 2TB|
| | |
| 16 | 128GB 256GB 512GB 1TB 2TB 2TB 2TB 2TB|
| | |
| 32 | 512GB 1TB 2TB 2TB 2TB 2TB 2TB 2TB|
| | |
| 64 | 2TB 2TB 2TB 2TB 2TB 2TB 2TB 2TB|
|___________|_________________________________________________________|
Page 3 Reliant UNIX 5.44 Printed 11/98
mkfs(1M-vxfs) (VxFS) mkfs(1M-vxfs)
Maximum file sizes for different iaddrlen values and a bsize value of
2 KB:
______________________________________________________________________
| bsize 2 KB | indsize (blocks) |
| | |
| iaddrlen | 4 8 16 32 64 128 256 512 1024|
| (blocks) | |
|||
| | |
| 4 | 32GB 64GB 128GB 256GB 512GB 1TB 2TB 4TB 4TB |
| | |
| 8 | 128GB 256GB 512GB 1TB 2TB 4TB 4TB 4TB 4TB |
| | |
| 16 | 512GB 1TB 2TB 4TB 4TB 4TB 4TB 4TB 4TB |
| | |
| 32 | 2TB 4TB 4TB 4TB 4TB 4TB 4TB 4TB 4TB |
|____________|________________________________________________________|
Maximum file sizes for different iaddrlen values and a bsize value of
4 KB:
______________________________________________________________________
| bsize 4 KB| indsize (blocks) |
| | |
| iaddrlen | 2 4 8 16 32 ... 512 1024|
| (blocks) | |
|||
| | |
| 2 | 32GB 64GB 128GB 256GB 512GB ... 8TB 8TB|
| | |
| 4 | 128GB 256GB 512GB 1TB 2TB ... 8TB 8TB|
| | |
| 8 | 512GB 1TB 2TB 4TB 8TB ... 8TB 8TB|
| | |
| 16 | 2TB 4TB 8TB 8TB 8TB ... 8TB 8TB|
|___________|_________________________________________________________|
Page 4 Reliant UNIX 5.44 Printed 11/98
mkfs(1M-vxfs) (VxFS) mkfs(1M-vxfs)
Maximum file sizes for different iaddrlen values and a bsize value of
8 KB:
______________________________________________________________________
| bsize 8 KB| indsize (blocks) |
| | |
| iaddrlen | 1 2 4 8 16 ... 512 1024|
| (blocks) | |
|||
| | |
| 1 | 32GB 64GB 128GB 256GB 512GB ... 16TB 16TB|
| | |
| 2 | 128GB 256GB 512GB 1TB 2TB ... 16TB 16TB|
| | |
| 4 | 512GB 1TB 2TB 4TB 8TB ... 16TB 16TB|
| | |
| 8 | 2TB 4TB 8TB 16TB 16TB ... 16TB 16TB|
|___________|_________________________________________________________|
SEE ALSO
fsck(1M), mkfs(1M), fs(4-vxfs).
Page 5 Reliant UNIX 5.44 Printed 11/98