mkfs.minix

Create a Minix filesystem inside partition Y on device X

$ sudo mkfs.minix [/dev/sdXY]

mkfs.minix [ -c | -l ] [ -n number-of-inodes ] [ -i ] [ -z ] device [ blocks ]

-c
    Check the device for bad blocks before creating the filesystem. Bad blocks will be marked and not used.

-l
    List bad blocks on the device instead of creating a filesystem. This option causes mkfs.minix to only scan and report.

-n number-of-inodes
    Specify the exact number of inodes to create. If omitted, mkfs.minix automatically determines the number of inodes based on the number of blocks, usually 1 inode for every 16 blocks.

-i
    Do not prompt for confirmation before proceeding. Use with extreme caution as this can overwrite important data without warning.

-z
    Zero-fill the entire device before creating the filesystem. This securely erases any previous data on the device and can also be used as a quick wipe method.

device
    The special file representing the block device or partition to be formatted (e.g., /dev/fd0, /dev/sdb1).

blocks
    The total number of blocks on the device to be used for the filesystem. If omitted, mkfs.minix automatically determines the device size and uses all available blocks.

mkfs.minix is a command-line utility used to format a storage device (like a disk partition or floppy disk) with the Minix filesystem structure. Originally developed by Linus Torvalds for the Minix operating system, it was a precursor to Linux's own filesystems. It sets up the boot block, super block, inode tables, and data blocks, preparing the device for data storage.

While historically significant, Minix filesystems have limitations in size and features compared to modern filesystems like Ext4, making them less common in contemporary Linux systems. It's often used for educational purposes or on very small embedded systems where its simplicity and compact nature are advantageous.

Minix filesystems have significant limitations compared to modern filesystems. They are hard-limited to 65536 blocks (typically 64MB if using 1KB block size) and 65536 inodes. This makes them unsuitable for most contemporary storage requirements and large datasets.

The Minix filesystem is renowned for its simple and transparent structure. It comprises a boot block, a superblock (containing vital filesystem metadata), an inode bitmap, a zone (data block) bitmap, an inode table, and data zones. This clear organization made it an excellent learning tool for understanding basic filesystem concepts and facilitated early operating system development.

While largely superseded by modern, feature-rich filesystems, mkfs.minix still finds niche applications. It is frequently used in educational settings to demonstrate fundamental filesystem principles, on extremely small or resource-constrained embedded systems where its minimal overhead is beneficial, or for historical purposes when dealing with legacy Minix systems.

mkfs.minix holds a significant place in Linux history. It was authored by Linus Torvalds himself, as the Minix operating system and its filesystem were instrumental in the early development of Linux. This command was the primary utility for preparing storage in the nascent Linux environment before the creation and widespread adoption of more advanced filesystems like ext2. Its simple design and functionality were well-suited for the limited hardware resources and development focus of the early 1990s.

fsck.minix(8), mount(8), mkfs(8), mkfs.ext4(8)