Filesystem Mounting

Filesystem Mounting refers to the process by which a filesystem is made accessible to the operating system and user by attaching it to a specific directory within the existing directory hierarchy. Instead of accessing storage devices or partitions directly, the system accesses their contents through a mount point, a directory that acts as the entry point to the mounted filesystem. Mounting integrates the filesystem into a unified namespace, allowing seamless access to files and directories across different storage devices.

Concept and Purpose of Filesystem Mounting

In Unix-like operating systems such as Alpine Linux, the filesystem is structured as a single hierarchical tree starting from the root directory /. Different filesystems, which may reside on various physical devices (hard drives, SSDs, USB drives, network shares), are not automatically part of this tree at boot. Mounting is the act of associating these filesystems with directories in the tree, making their data accessible under those directories.

Without mounting, a filesystem on a device remains isolated and cannot be used by normal file operations. Mounting enables the OS to translate file access requests within the mount point directory into operations on the underlying device.

Mount Points and Their Characteristics

A mount point is an existing empty directory in the current filesystem hierarchy where another filesystem is attached. When a filesystem is mounted on this directory, the original content of the directory becomes hidden and replaced by the root of the mounted filesystem. Unmounting the filesystem restores visibility of the original directory contents.

Mount points must exist before mounting occurs, and they can be any directory, commonly created explicitly for this purpose (e.g., /mnt, /media/usb, /home).

Filesystem Types and Mounting

Different filesystems can be mounted, including but not limited to:

• Ext4, Ext3, Ext2 (common Linux filesystems)
• XFS, Btrfs (advanced Linux filesystems)
• FAT, NTFS (commonly used for compatibility with Windows systems)
• NFS (Network File System for remote mounts)
• tmpfs (temporary in-memory filesystems)

The kernel must support the filesystem type to mount it successfully, either built-in or through loadable modules.

Mounting Process and Commands

Mounting can be performed manually or automatically:

• Manual Mounting: Using the mount command, a user or administrator can mount a filesystem specifying the source device or resource and the target mount point.

Example:

mount /dev/sda1 /mnt/data

This command attaches the filesystem found on /dev/sda1 to the directory /mnt/data.

• Automatic Mounting: During system boot, filesystems specified in the /etc/fstab file are automatically mounted. The fstab file includes device identifiers, mount points, filesystem types, mount options, and dump/pass flags.

Example entry in /etc/fstab:

/dev/sda1  /mnt/data  ext4  defaults  0  2

Mount Options and Their Effects

Mount options control the behavior of the mounted filesystem. Common options include:

• ro (read-only): Mounts the filesystem read-only.
• rw (read-write): Default; allows reading and writing.
• noexec: Prevents execution of binaries on the filesystem.
• nosuid: Ignores set-user-identifier or set-group-identifier bits.
• nodev: Disallows device files on the filesystem.
• sync: All I/O to the filesystem is done synchronously.
• async: Allows asynchronous I/O (default).
• user / users: Allows non-root users to mount or unmount.

Custom options may exist depending on the filesystem type.

Unmounting Filesystems

Unmounting is the reverse process of mounting, detaching the filesystem from its mount point and restoring access to the underlying directory content. The umount command is used for this purpose.

Example:

umount /mnt/data

Unmounting is necessary before removing physical devices or making low-level changes to the filesystem to avoid data corruption.

Mount Namespace and Isolation in Alpine Linux

Alpine Linux, like other modern Linux distributions, supports mount namespaces, allowing containers or processes to have isolated views of the filesystem hierarchy. This is crucial in containerization where each container can have its own mount points independent of the host or other containers.

Mount namespaces enable flexible and secure mounting strategies without affecting the global system mount table.

Mounting tmpfs and Virtual Filesystems

Alpine Linux extensively uses virtual filesystems such as tmpfs to mount temporary filesystems in memory. These filesystems provide fast, volatile storage for runtime data like /tmp or /run.

Example mount command for tmpfs:

mount -t tmpfs tmpfs /tmp

Virtual filesystems such as proc and sysfs are also mounted during boot to provide kernel and process information in a filesystem interface.

Troubleshooting Mounting Issues

Common issues during mounting include:

• Incorrect device or path specification.
• Missing or non-existent mount points.
• Unsupported filesystem types.
• Permission or privilege restrictions.
• Filesystem corruption or errors.

Tools such as dmesg, mount, umount, and logs in /var/log assist in diagnosing mounting problems.

Summary of Key Commands

Filesystem mounting is foundational to managing storage in Alpine Linux, enabling flexible and dynamic integration of diverse filesystems into a unified directory hierarchy for seamless file access and management.