Why Linux Mounts Removable Media in /mnt and /media

In the Linux operating system, storage devices do not use drive letters like Windows; instead, they are attached to specific directories within a single, unified filesystem tree. Removable storage devices such as USB flash drives, external hard drives, and optical discs are traditionally mounted inside the /mnt or /media directories to conform to the Filesystem Hierarchy Standard (FHS). While both directories serve as designated access points for temporary storage, /mnt was historically designed for system administrators to mount filesystems manually, whereas /media was introduced to allow modern desktop environments to automatically detect and mount removable devices safely and predictably.

The Unified Directory Tree and Mount Points

Unlike operating systems that assign letters like C: or D: to physical partitions, Linux treats everything as a file, organizing all data under a single root directory (/). For a storage device to become accessible, its filesystem must be "mounted"—or grafted—onto an existing directory.

Because mounting a device onto an arbitrary system folder could obscure vital system files or create confusion, standardized locations were established to keep the root directory organized and secure.

The Historic Role of /mnt

The /mnt directory—short for "mount"—is one of the oldest standard locations in Unix and Linux history.

• Manual Administration: System administrators use /mnt to manually attach filesystems on a temporary basis. For example, during system recovery, disk repairs, or network filesystem testing, an admin might mount a partition using the mount /dev/sdb1 /mnt command.
• Temporary Use: Under the Filesystem Hierarchy Standard, /mnt is explicitly defined as a temporary mount point. It was never intended to support multiple, constantly changing consumer devices simultaneously. When desktop environments began auto-mounting multiple devices like floppy disks, CDs, and flash drives at the same time, using /mnt directly caused clutter and namespace collisions.

The Introduction of /media

To resolve the limitations of /mnt, the Filesystem Hierarchy Standard introduced /media in FHS version 2.3.

• Automated Device Handling: Modern desktop Linux distributions use background services (such as udev and udisks) to detect when a hardware device is plugged in. The system automatically creates a subfolder inside /media—often structured as /media/<username>/<device_label>—and mounts the device there without requiring root privileges or manual terminal commands.
• Dynamic Clean-up: When the user unmounts and ejects the removable medium, the system automatically removes the temporary directory it created inside /media, ensuring the filesystem stays clean.
• Separation of Concerns: By segregating automated user devices into /media, the system preserves /mnt for administrators who need a clean, static, and predictable location to mount filesystems manually without interference from desktop automation tools.

Summary of Differences

• /mnt: Intended for the system administrator to manually mount temporary filesystems (such as network shares, secondary recovery drives, or disk images) via the command line.
• /media: Intended for the operating system to automatically mount user-level, physical removable media (such as USB thumb drives, external HDDs, and SD cards).