mkfs_vxfs(1M)

Do not write the file system to the special file. This option gives all the information needed to create a file system but does not create it.

Create a file system in a file. This is used for debugging purposes only.

n is the VxFS disk layout version number. n can be 2 or 3 to indicate the Version 2 or Version 3 disk layout. Version 2 supports dynamic inode allocation. Version 3 adds support for large files and large UIDs. The default is the Version 3.

n is the on-disk inode structure size for files on the file system. The only allowed value is 256 bytes.

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 2 selected from the range 1024 to 8192. The default is 1024.

n is the maximum number of inodes in the file system. The actual maximum number of inodes is n rounded up to an appropriate boundary. For a Version 2 or 3 disk layout this is the maximum number of inodes, The number 0 and the string ``unlimited'' are interpreted to mean that the number of inodes is unlimited. The default is ``unlimited'' for a Version 2 or 3 disk layout.

n is the number of allocation units on the file system. If nau is specified, then ausize is determined by evenly dividing the sectors among the allocation units. By default, the number of allocation units will be set based on the value of ausize. This option is ignored for a Version 3 disk layout.

n is the size, in blocks of size bsize, of an allocation unit. This is an alternate way of specifying the number of allocation units. This option may not be used in conjunction with the nau option. With this option, the last 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. This parameter may not exceed 262144 blocks.

The algorithm used to choose the default value is rather complicated, but is intended to balance the number of allocation units (4 to 16 is a good range), the size of the allocation units (at least 32768 blocks), and other factors. For a Version 3 disk layout the allocation unit size is fixed at 32768 blocks, and this option is ignored.

n is the starting block number, in blocks of size bsize, of the first allocation unit. This option allows the allocation units to be aligned to a particular boundary, such as a cylinder boundary. For a Version 3 file system, aufirst is always 0, and this option is ignored.

n is the size, in blocks of size bsize, 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. For a Version 3 file system, aupad is always 0, and this option is ignored.

n is the number of blocks to allocate for an activity logging area. n must be in the range 32 blocks to 16384 Kbytes. Although logsize is specified in blocks, the maximum value is 16384 Kbytes. This means that for a bsize of 1024, 2048, 4096, or 8192 bytes the maximum value of logsize is 16384, 8192, 4096, or 2048 blocks, respectively. To avoid wasting space, the default logsize is 1024 blocks for a file system 8 megabytes or larger, 128 blocks for a file system 2 megabytes or larger but less than 8 megabytes, and 32 blocks for a file system less than 2 megabytes.

Controls the largefile compatibility bit for the file system. By default the bit is not set, and files created on the file system will be limited to less than 2 gigabytes in size. If largefiles is specified, the bit is set and the maximum file size for files created on the file system is not limited to 2 gigabytes (see mount_vxfs(1M) and fsadm_vxfs(1M)). This option is only valid for a Version 3 disk layout. The default is nolargefiles, although the default may change in the future.