mkfs.minix

Create a Minix filesystem inside partition Y on device X

$ mkfs.minix [/dev/sdXY]

mkfs.minix [-c | -l bad-blocks-file] [-n sector-size] [-i inodes] device [size]

-c
    Check the device for bad blocks before creating the filesystem.
This can take a significant amount of time.

-l bad-blocks-file
    Read the list of bad blocks from bad-blocks-file.

-n sector-size
    Specify the sector size in bytes. Must be a power of 2 and greater than or equal to 512.
Older versions of mkfs.minix did not require this option but modern kernels often do.

-i inodes
    Specify the number of inodes for the filesystem.
If not specified, a default value is used based on the filesystem size.

device
    The device (e.g., /dev/sda1) where the filesystem will be created.

size
    The size of the filesystem in blocks (optional).
If not provided, mkfs.minix will determine it from the device size.

The mkfs.minix command is used to create a Minix filesystem on a specified device (e.g., a disk partition or a file). It initializes the filesystem's metadata structures, such as the superblock, inode table, and zone bitmap, making the device usable for storing files and directories within the Minix filesystem format. The Minix filesystem was one of the first filesystems available under Linux and is relatively simple compared to modern filesystems like ext4 or XFS. mkfs.minix is useful for creating small, simple filesystems, often in embedded systems or for educational purposes, and may not provide advanced features such as journaling or large file support.

mkfs.minix will erase all existing data on the specified device. Be extremely careful when specifying the device, as writing to the wrong device can lead to data loss. The Minix filesystem has limitations in terms of file size and overall capacity compared to modern filesystems. It is not suitable for general-purpose use on modern systems.

While not common on modern servers, mkfs.minix can be useful in embedded systems, creating small ramdisks, or for educational purposes when demonstrating basic filesystem concepts. It may also be used for interoperability with older systems that still rely on the Minix filesystem format.

If mkfs.minix fails to create the filesystem, it's often due to problems with the device (e.g., bad sectors) or incorrect parameters. Examine the output carefully for error messages and check the system logs for more details.

The Minix filesystem was developed by Andrew S. Tanenbaum for the MINIX operating system, which was created for educational purposes. mkfs.minix was the utility created to make such partitions usable as filesystems. When Linux was initially developed, it used a version of the Minix filesystem due to its simplicity and ease of implementation. Over time, Linux development moved towards more advanced and robust filesystems, making mkfs.minix less frequently used in typical desktop or server environments.

mount(8), umount(8), fsck.minix(8)