Storage and Filesystems

Storage and Filesystems encompass the management, organization, and access methods for data stored on physical or virtual devices within an operating system. It involves the handling of storage devices, the partitioning of disks, the creation and selection of filesystems, mounting these filesystems for use, and configuring persistent mounts to ensure availability across system reboots. Storage and Filesystems also cover the management of swap space, logical volume management for flexible storage allocation, software RAID for redundancy and performance, encryption for data security, and support for removable storage devices.

Storage Devices and Block Devices

Storage devices are physical or virtual hardware components used to persistently store digital data. Common storage devices include hard disk drives (HDDs), solid-state drives (SSDs), USB flash drives, and optical media. In Linux-based systems like Alpine Linux, these devices are exposed as block devices, which provide random-access storage in fixed-size blocks, typically 512 bytes or multiples thereof.

Block devices are represented in the system under the /dev directory with names such as /dev/sda, /dev/sdb, etc., with partitions represented as /dev/sda1, /dev/sda2, and so forth. These devices allow read and write operations at the block level, which is essential for managing filesystems and data structures.

Disk Partitioning

Disk partitioning divides a storage device into distinct regions called partitions. Each partition can be treated as an independent storage volume, allowing multiple filesystems or operating systems on a single physical device.

Partitioning schemes include:

• MBR (Master Boot Record): Traditional partitioning limited to four primary partitions and a maximum disk size of 2 TiB.
• GPT (GUID Partition Table): Modern scheme supporting large disks, many partitions, and redundancy.

Partitioning tools such as fdisk, parted, and cfdisk allow users to create, delete, and modify partitions. Partitions are formatted with filesystems or used for other storage purposes like swap or LVM.

Filesystem Creation and Selection

A filesystem is a data structure and set of algorithms used to organize and store files on a partition or storage device. Filesystem creation involves formatting a partition or device with a specific filesystem type, which prepares the space for file storage.

Common filesystem types in Alpine Linux include:

• ext4: A widely used Linux filesystem offering robustness, journaling, and high performance.
• xfs: High-performance journaling filesystem suitable for large files and parallel I/O.
• btrfs: A modern filesystem with advanced features like snapshots, checksumming, and pooling.
• FAT32 and exFAT: Filesystems for interoperability with other operating systems and removable media.
• swap: Special pseudo-filesystem used for virtual memory.

Filesystem selection depends on use cases, performance needs, compatibility, and feature requirements.

Creation commands examples:

mkfs.ext4 /dev/sda1
mkfs.xfs /dev/sdb1
mkswap /dev/sdc1

Filesystem Mounting

Mounting is the process of making a filesystem accessible at a specific directory (mount point) within the system's directory tree. After mounting, files and directories on the storage device become part of the unified filesystem hierarchy.

Mounting can be done manually with the mount command:

mount /dev/sda1 /mnt/data

Unmounting is performed with umount to safely detach the filesystem.

Filesystems can be mounted with options that control behavior, such as read-only mode, no-execute, or user access permissions. The mount command syntax supports these options for fine-tuning.

Persistent Mount Configuration

To ensure filesystems remain mounted after system reboots, persistent mount configurations are required. This is typically done by editing the /etc/fstab file, which lists devices, mount points, filesystem types, and mount options.

An example /etc/fstab entry:

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

This instructs the system to mount /dev/sda1 at /mnt/data automatically with default options during boot.

UUIDs or labels can be used instead of device names to uniquely identify partitions, improving reliability in dynamic device environments.

Swap

Swap space acts as an extension of physical RAM by providing disk space for temporarily holding inactive memory pages. This prevents system crashes from memory exhaustion and can improve system responsiveness under load.

Swap can be configured as a dedicated partition or a swap file. Enabling swap involves creating the swap area and activating it:

mkswap /dev/sda2
swapon /dev/sda2

The /etc/fstab entry enables persistent swap activation:

/dev/sda2  none  swap  sw  0  0

Logical Volume Management (LVM)

Logical Volume Management abstracts physical storage devices into flexible logical volumes, allowing dynamic resizing, snapshots, and aggregation of multiple physical volumes.

Key LVM components:

• Physical Volumes (PV): Actual storage devices or partitions.
• Volume Groups (VG): Pools of storage created from PVs.
• Logical Volumes (LV): Virtual partitions carved from VGs, used to create filesystems.

LVM commands (pvcreate, vgcreate, lvcreate) manage these components, providing flexibility for storage allocation and management, such as resizing volumes without downtime.

Software RAID

Software RAID (Redundant Array of Independent Disks) combines multiple physical disks into a single logical unit to improve redundancy, performance, or both.

Common RAID levels:

• RAID 0 (Striping): Increases performance by spreading data across disks; no redundancy.
• RAID 1 (Mirroring): Duplicates data on two disks for redundancy.
• RAID 5, 6: Use parity for fault tolerance with multiple disks.
• RAID 10: Combines mirroring and striping.

Linux uses the mdadm utility to create and manage software RAID arrays. RAID arrays appear as block devices and can be formatted with filesystems and mounted like regular partitions.

Storage Encryption

Storage encryption protects data at rest by encoding it to prevent unauthorized access. In Alpine Linux, encryption is commonly implemented via Linux Unified Key Setup (LUKS) on top of block devices.

The encrypted device must be unlocked with a passphrase or key before use, after which it can be formatted with a filesystem and mounted normally.

Typical workflow:

1. Initialize encryption:

cryptsetup luksFormat /dev/sda3

2. Open encrypted device:

cryptsetup luksOpen /dev/sda3 encrypted_volume

3. Format and mount the mapped device /dev/mapper/encrypted_volume.

Encrypted volumes can also be integrated with LVM for flexible encrypted storage.

Removable Storage

Removable storage devices such as USB drives, SD cards, and external HDDs are supported by the system with dynamic detection and mounting facilities.

Automounting tools or manual mounting allow access to filesystems on these devices, which commonly use FAT32, exFAT, or NTFS for compatibility.

Unmounting removable devices safely before removal is essential to prevent data loss.

Storage and Filesystems in Alpine Linux thus cover a comprehensive set of technologies and practices for storing, organizing, protecting, and accessing persistent data in a secure, efficient, and flexible manner.