{"id":161425,"date":"2026-03-19T02:25:35","date_gmt":"2026-03-18T23:25:35","guid":{"rendered":"https:\/\/cloudspinx.com\/?p=73954"},"modified":"2026-03-19T02:25:57","modified_gmt":"2026-03-18T23:25:57","slug":"lpic-101-partitions-filesystems-linux","status":"publish","type":"post","link":"https:\/\/computingforgeeks.com\/lpic-101-partitions-filesystems-linux\/","title":{"rendered":"LPIC 101 – Managing Partitions and Filesystems on Linux"},"content":{"rendered":"\n

Managing partitions and filesystems is one of the most critical skills tested on the LPIC-1 (101-500) exam. Whether you are setting up a fresh server, expanding storage on a production box, or recovering from a disk failure at 2 AM, you need to know these tools cold. This guide covers every partition and filesystem topic you will encounter on the exam, with real command examples and explanations that go beyond surface-level theory.<\/p>\n\n\n\n

This post maps directly to LPIC-1 Objective 104.1<\/strong> (Create partitions and filesystems), 104.2<\/strong> (Maintain the integrity of filesystems), and 104.3<\/strong> (Control mounting and unmounting of filesystems). We also touch on Objective 102.1<\/strong> (Design hard disk layout) where relevant.<\/p>\n\n\n\n

1. Linux Disk Naming Conventions<\/h2>\n\n\n\n

Before you touch any partitioning tool, you need to understand how Linux names its block devices. The kernel assigns device nodes under \/dev\/<\/code> based on the controller type and detection order.<\/p>\n\n\n\n

SCSI\/SATA\/USB Disks (\/dev\/sd*)<\/h3>\n\n\n\n

Traditional SATA drives, SAS drives, and USB storage all appear as \/dev\/sda<\/code>, \/dev\/sdb<\/code>, \/dev\/sdc<\/code>, and so on. The letter increments with each detected device. Partitions on these disks are numbered: \/dev\/sda1<\/code>, \/dev\/sda2<\/code>, \/dev\/sda3<\/code>.<\/p>\n\n\n\n

For MBR-partitioned disks, primary partitions are numbered 1 through 4. Logical partitions inside an extended partition always start at number 5, regardless of how many primary partitions exist.<\/p>\n\n\n\n

NVMe Disks (\/dev\/nvme*)<\/h3>\n\n\n\n

NVMe SSDs use a different naming scheme. The controller is \/dev\/nvme0<\/code>, the first namespace (think “disk”) on that controller is \/dev\/nvme0n1<\/code>, and partitions are \/dev\/nvme0n1p1<\/code>, \/dev\/nvme0n1p2<\/code>, etc. A second NVMe controller would be \/dev\/nvme1<\/code>.<\/p>\n\n\n\n

VirtIO Disks (\/dev\/vd*)<\/h3>\n\n\n\n

Virtual machines running on KVM\/QEMU with the VirtIO driver expose disks as \/dev\/vda<\/code>, \/dev\/vdb<\/code>, etc. Partitions follow the same pattern as SCSI: \/dev\/vda1<\/code>, \/dev\/vda2<\/code>. You will see these on every major cloud provider that runs KVM underneath.<\/p>\n\n\n\n

You can always check what block devices the kernel sees with:<\/p>\n\n\n\n

lsblk<\/code><\/pre>\n\n\n\n
That command gives you a tree view of all disks, partitions, and their mount points. It is one of the first commands you should run when troubleshooting storage.<\/p>\n\n\n\n
2. Partition Tables: MBR vs GPT<\/h2>\n\n\n\n
Every disk needs a partition table before you can carve it into usable partitions. Linux supports two types, and the LPIC exam expects you to know both thoroughly.<\/p>\n\n\n\n
MBR (Master Boot Record)<\/h3>\n\n\n\n
MBR has been around since 1983. The partition table lives in the first 512 bytes of the disk. Key limitations:<\/p>\n\n\n\n
    \n
  • Maximum disk size of 2 TiB (2,199,023,255,552 bytes)<\/li>\n
  • Maximum of 4 primary partitions<\/li>\n
  • To get more than 4 partitions, you sacrifice one primary slot for an extended partition, which then holds logical partitions<\/li>\n
  • No built-in redundancy for the partition table itself<\/li>\n<\/ul>\n\n\n\n
    MBR is still used on older systems, small disks, and legacy BIOS boot setups. If you are working with disks under 2 TiB and need BIOS boot compatibility, MBR works fine.<\/p>\n\n\n\n
    GPT (GUID Partition Table)<\/h3>\n\n\n\n
    GPT is part of the UEFI specification and removes nearly every MBR limitation:<\/p>\n\n\n\n
      \n
    • Supports disks up to 9.4 ZB (zettabytes) in theory<\/li>\n
    • Up to 128 partitions by default (no need for extended\/logical partitions)<\/li>\n
    • Each partition is identified by a unique GUID<\/li>\n
    • The partition table is stored at the beginning and end of the disk, providing redundancy<\/li>\n
    • Includes CRC32 checksums for integrity verification<\/li>\n<\/ul>\n\n\n\n
      Use GPT for any disk over 2 TiB, any UEFI system, and any new installation where you have no reason to stick with MBR. Modern Linux distributions default to GPT.<\/p>\n\n\n\n
      3. Partitioning with fdisk (MBR Disks)<\/h2>\n\n\n\n
      fdisk<\/code> is the classic interactive partitioning tool for MBR disks. Modern versions of fdisk can also handle GPT, but for the exam, associate fdisk with MBR and gdisk with GPT.<\/p>\n\n\n\n
      List all partitions on the system:<\/p>\n\n\n\n
      sudo fdisk -l<\/code><\/pre>\n\n\n\n
      To work on a specific disk interactively:<\/p>\n\n\n\n
      sudo fdisk \/dev\/sdb<\/code><\/pre>\n\n\n\n
      Once inside the fdisk prompt, these are the commands you need to memorize:<\/p>\n\n\n\n
        \n
      • p<\/strong> – Print the current partition table<\/li>\n
      • n<\/strong> – Create a new partition<\/li>\n
      • d<\/strong> – Delete a partition<\/li>\n
      • t<\/strong> – Change the partition type (e.g., 82 for Linux swap, 83 for Linux, 8e for Linux LVM)<\/li>\n
      • w<\/strong> – Write changes to disk and exit<\/li>\n
      • q<\/strong> – Quit without saving<\/li>\n
      • m<\/strong> – Display the help menu<\/li>\n<\/ul>\n\n\n\n
        Here is a typical workflow for creating a new primary partition. After running sudo fdisk \/dev\/sdb<\/code>, you would press n<\/code> for a new partition, p<\/code> for primary, accept the default partition number, accept the default first sector, then type +10G<\/code> to make it 10 GiB. Press w<\/code> to write and exit.<\/p>\n\n\n\n
        After writing the partition table, inform the kernel about the changes:<\/p>\n\n\n\n
        sudo partprobe \/dev\/sdb<\/code><\/pre>\n\n\n\n
        The partprobe<\/code> command re-reads the partition table without requiring a reboot. On older kernels, you might need to use partx -a \/dev\/sdb<\/code> instead.<\/p>\n\n\n\n
        4. Partitioning with gdisk (GPT Disks)<\/h2>\n\n\n\n
        gdisk<\/code> is the GPT counterpart to fdisk. The interface is deliberately similar, so if you know fdisk, you already know most of gdisk.<\/p>\n\n\n\n
        sudo gdisk \/dev\/sdc<\/code><\/pre>\n\n\n\n
        Key commands inside gdisk:<\/p>\n\n\n\n
          \n
        • p<\/strong> – Print the partition table<\/li>\n
        • n<\/strong> – Create a new partition<\/li>\n
        • d<\/strong> – Delete a partition<\/li>\n
        • t<\/strong> – Change partition type code (uses GUID type codes like 8300 for Linux filesystem, 8200 for Linux swap, 8e00 for Linux LVM)<\/li>\n
        • i<\/strong> – Show detailed info about a partition<\/li>\n
        • w<\/strong> – Write changes and exit<\/li>\n
        • q<\/strong> – Quit without saving<\/li>\n<\/ul>\n\n\n\n
          Creating a partition in gdisk follows the same flow as fdisk. The main difference is the partition type codes. GPT type codes are four hex digits (like 8300) instead of the two-digit MBR codes (like 83).<\/p>\n\n\n\n
          One important gdisk feature: you can convert an MBR disk to GPT with the r<\/code> (recovery) menu followed by f<\/code> (load MBR and convert to GPT). Do this with extreme care on production systems and always have a backup.<\/p>\n\n\n\n
          5. Partitioning with parted (MBR and GPT)<\/h2>\n\n\n\n
          parted<\/code> handles both MBR and GPT disks and, unlike fdisk and gdisk, can resize partitions. This makes it the most versatile partitioning tool in the Linux toolkit.<\/p>\n\n\n\n
          Launch parted on a specific disk:<\/p>\n\n\n\n
          sudo parted \/dev\/sdd<\/code><\/pre>\n\n\n\n
          Print the current partition layout:<\/p>\n\n\n\n
          (parted) print<\/code><\/pre>\n\n\n\n
          Create a GPT partition table on a new disk:<\/p>\n\n\n\n
          (parted) mklabel gpt<\/code><\/pre>\n\n\n\n
          For an MBR table, use mklabel msdos<\/code> instead. Create a partition spanning from 1 MiB to 20 GiB:<\/p>\n\n\n\n
          (parted) mkpart primary ext4 1MiB 20GiB<\/code><\/pre>\n\n\n\n
          Resize a partition (this is where parted shines):<\/p>\n\n\n\n
          (parted) resizepart 1 40GiB<\/code><\/pre>\n\n\n\n
          Critical warning:<\/strong> parted writes changes immediately. There is no “write and quit” step like fdisk. Every command you run takes effect on the disk right away. Double-check your commands before pressing Enter.<\/p>\n\n\n\n
          You can also run parted in non-interactive (scripted) mode, which is useful for automation:<\/p>\n\n\n\n
          sudo parted -s \/dev\/sdd mkpart primary ext4 1MiB 20GiB<\/code><\/pre>\n\n\n\n
          The -s<\/code> flag suppresses the interactive prompts.<\/p>\n\n\n\n
          6. Creating Filesystems with mkfs<\/h2>\n\n\n\n
          A partition without a filesystem is just raw space. The mkfs<\/code> family of commands formats partitions with the filesystem of your choice. The LPIC exam covers four filesystem types in detail.<\/p>\n\n\n\n
          ext4<\/h3>\n\n\n\n
          ext4 is the default filesystem on most Linux distributions. It is mature, well-tested, and handles general-purpose workloads reliably. Key features:<\/p>\n\n\n\n
            \n
          • Maximum volume size: 1 EiB<\/li>\n
          • Maximum file size: 16 TiB<\/li>\n
          • Journaling (metadata and optionally data)<\/li>\n
          • Extents-based allocation for reduced fragmentation<\/li>\n
          • Backward compatible with ext2 and ext3<\/li>\n
          • Online resizing (grow only)<\/li>\n<\/ul>\n\n\n\n
            Create an ext4 filesystem:<\/p>\n\n\n\n
            sudo mkfs.ext4 \/dev\/sdb1<\/code><\/pre>\n\n\n\n
            Add a label during creation for easier identification:<\/p>\n\n\n\n
            sudo mkfs.ext4 -L \"data_vol\" \/dev\/sdb1<\/code><\/pre>\n\n\n\n
            XFS<\/h3>\n\n\n\n
            XFS is the default on RHEL\/CentOS\/Rocky Linux. It excels at handling large files and parallel I\/O. Key features:<\/p>\n\n\n\n
              \n
            • Maximum volume size: 8 EiB<\/li>\n
            • Maximum file size: 8 EiB<\/li>\n
            • Excellent performance for large sequential writes<\/li>\n
            • Allocation groups allow parallel I\/O operations<\/li>\n
            • Online resizing (grow only, cannot shrink)<\/li>\n
            • Online defragmentation with xfs_fsr<\/code><\/li>\n<\/ul>\n\n\n\n
              Create an XFS filesystem:<\/p>\n\n\n\n
              sudo mkfs.xfs \/dev\/sdb2<\/code><\/pre>\n\n\n\n
              If the partition already has a filesystem and you want to overwrite it:<\/p>\n\n\n\n
              sudo mkfs.xfs -f \/dev\/sdb2<\/code><\/pre>\n\n\n\n
              Btrfs<\/h3>\n\n\n\n
              Btrfs (B-tree filesystem) is a copy-on-write filesystem with advanced features. openSUSE uses it as the default. Key features:<\/p>\n\n\n\n
                \n
              • Maximum volume size: 16 EiB<\/li>\n
              • Built-in snapshots and subvolumes<\/li>\n
              • Transparent compression (zlib, lzo, zstd)<\/li>\n
              • Built-in RAID support (RAID 0, 1, 10)<\/li>\n
              • Online resizing (grow and shrink)<\/li>\n
              • Data and metadata checksumming<\/li>\n<\/ul>\n\n\n\n
                Create a Btrfs filesystem:<\/p>\n\n\n\n
                sudo mkfs.btrfs \/dev\/sdb3<\/code><\/pre>\n\n\n\n
                vfat (FAT32)<\/h3>\n\n\n\n
                vfat is the Linux implementation of Microsoft’s FAT32. You will use it for EFI System Partitions (ESP) and USB drives that need to work across operating systems. Key features:<\/p>\n\n\n\n
                  \n
                • Maximum file size: 4 GiB<\/li>\n
                • Maximum volume size: 2 TiB (with 512-byte sectors)<\/li>\n
                • No file permissions, no journaling, no symlinks<\/li>\n
                • Universal cross-platform compatibility<\/li>\n<\/ul>\n\n\n\n
                  Create a FAT32 filesystem:<\/p>\n\n\n\n
                  sudo mkfs.vfat -F 32 \/dev\/sdb4<\/code><\/pre>\n\n\n\n
                  The -F 32<\/code> flag explicitly selects FAT32 rather than FAT12 or FAT16.<\/p>\n\n\n\n
                  7. Mounting Filesystems<\/h2>\n\n\n\n
                  Creating a filesystem is only half the job. You need to mount it to make it accessible. Linux gives you several ways to handle this.<\/p>\n\n\n\n
                  Manual Mounting with mount<\/h3>\n\n\n\n
                  Mount a filesystem to a directory:<\/p>\n\n\n\n
                  sudo mount \/dev\/sdb1 \/mnt\/data<\/code><\/pre>\n\n\n\n
                  The mount point directory must exist before you mount. If it does not:<\/p>\n\n\n\n
                  sudo mkdir -p \/mnt\/data<\/code><\/pre>\n\n\n\n
                  View all currently mounted filesystems:<\/p>\n\n\n\n
                  mount | column -t<\/code><\/pre>\n\n\n\n
                  Or for a cleaner output, use findmnt<\/code> which reads from \/proc\/self\/mountinfo<\/code>:<\/p>\n\n\n\n
                  findmnt --real<\/code><\/pre>\n\n\n\n
                  Mount Options<\/h3>\n\n\n\n
                  The -o<\/code> flag lets you specify mount options. These come up frequently on the exam:<\/p>\n\n\n\n
                    \n
                  • ro<\/strong> \/ rw<\/strong> – Mount read-only or read-write<\/li>\n
                  • noexec<\/strong> – Prevent execution of binaries on this filesystem<\/li>\n
                  • nosuid<\/strong> – Ignore SUID and SGID bits<\/li>\n
                  • nodev<\/strong> – Ignore device files on this filesystem<\/li>\n
                  • noatime<\/strong> – Do not update access times (improves performance)<\/li>\n
                  • relatime<\/strong> – Update atime only if older than mtime (default on most distros)<\/li>\n
                  • defaults<\/strong> – Equivalent to rw, suid, dev, exec, auto, nouser, async<\/li>\n<\/ul>\n\n\n\n
                    Example mounting with multiple options:<\/p>\n\n\n\n
                    sudo mount -o noexec,nosuid,nodev \/dev\/sdb1 \/mnt\/data<\/code><\/pre>\n\n\n\n
                    Remount an already-mounted filesystem with different options (no need to unmount first):<\/p>\n\n\n\n
                    sudo mount -o remount,ro \/mnt\/data<\/code><\/pre>\n\n\n\n
                    UUID vs Device Name<\/h3>\n\n\n\n
                    Device names like \/dev\/sdb1<\/code> can change between reboots if you add or remove disks. The kernel assigns letters based on detection order, so what was \/dev\/sdb<\/code> yesterday could become \/dev\/sdc<\/code> today.<\/p>\n\n\n\n
                    UUIDs solve this problem. Every filesystem gets a unique identifier when it is created, and that UUID never changes unless you reformat. Find the UUID with:<\/p>\n\n\n\n
                    sudo blkid \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                    Mount by UUID:<\/p>\n\n\n\n
                    sudo mount UUID=\"a1b2c3d4-5678-9abc-def0-123456789abc\" \/mnt\/data<\/code><\/pre>\n\n\n\n
                    Always use UUIDs in \/etc\/fstab<\/code> for production systems. This is not just a best practice; it is a reliability requirement.<\/p>\n\n\n\n
                    Persistent Mounts with \/etc\/fstab<\/h3>\n\n\n\n
                    The \/etc\/fstab<\/code> file defines filesystems that should be mounted automatically at boot. Each line has six fields:<\/p>\n\n\n\n
                    # <device\/UUID>                                <mount point>  <type>  <options>       <dump> <fsck order>\nUUID=a1b2c3d4-5678-9abc-def0-123456789abc  \/mnt\/data      ext4    defaults        0      2\nUUID=e5f6a7b8-1234-5678-9abc-def012345678  \/mnt\/backup    xfs     noatime,noexec  0      2\n\/dev\/sdb3                                  \/mnt\/scratch   btrfs   defaults        0      0<\/code><\/pre>\n\n\n\n
                    The six fields explained:<\/p>\n\n\n\n
                      \n
                    1. Device<\/strong> – UUID, device path, or LABEL<\/li>\n
                    2. Mount point<\/strong> – Where the filesystem appears in the directory tree<\/li>\n
                    3. Filesystem type<\/strong> – ext4, xfs, btrfs, vfat, swap, etc.<\/li>\n
                    4. Options<\/strong> – Mount options (defaults, noatime, noexec, etc.)<\/li>\n
                    5. Dump<\/strong> – Used by the dump backup utility (0 = skip, 1 = backup). Almost always 0 on modern systems.<\/li>\n
                    6. Fsck order<\/strong> – Order for filesystem checks at boot (0 = skip, 1 = root filesystem first, 2 = everything else)<\/li>\n<\/ol>\n\n\n\n
                      After editing fstab, test it before rebooting:<\/p>\n\n\n\n
                      sudo mount -a<\/code><\/pre>\n\n\n\n
                      This mounts everything in fstab that is not already mounted. If there is an error, you will see it immediately instead of discovering it during a reboot when the system drops to emergency mode.<\/p>\n\n\n\n
                      8. Managing Swap Space<\/h2>\n\n\n\n
                      Swap provides overflow space when physical RAM is full. Linux supports two forms: swap partitions and swap files. The LPIC exam tests both.<\/p>\n\n\n\n
                      Swap Partition<\/h3>\n\n\n\n
                      Create a partition with fdisk or gdisk and set its type to Linux swap (type 82 in fdisk, 8200 in gdisk). Then format and activate it:<\/p>\n\n\n\n
                      sudo mkswap \/dev\/sdb5<\/code><\/pre>\n\n\n\n
                      Activate the swap partition:<\/p>\n\n\n\n
                      sudo swapon \/dev\/sdb5<\/code><\/pre>\n\n\n\n
                      Verify it is active:<\/p>\n\n\n\n
                      swapon --show<\/code><\/pre>\n\n\n\n
                      Add it to \/etc\/fstab<\/code> for persistence across reboots:<\/p>\n\n\n\n
                      UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  none  swap  sw  0  0<\/code><\/pre>\n\n\n\n
                      Swap File<\/h3>\n\n\n\n
                      Swap files are more flexible than partitions because you can create and resize them without repartitioning. Create a 2 GiB swap file:<\/p>\n\n\n\n
                      sudo dd if=\/dev\/zero of=\/swapfile bs=1M count=2048<\/code><\/pre>\n\n\n\n
                      Set the correct permissions (swap files must not be world-readable):<\/p>\n\n\n\n
                      sudo chmod 600 \/swapfile<\/code><\/pre>\n\n\n\n
                      Format and enable:<\/p>\n\n\n\n
                      sudo mkswap \/swapfile\nsudo swapon \/swapfile<\/code><\/pre>\n\n\n\n
                      Add to fstab:<\/p>\n\n\n\n
                      \/swapfile  none  swap  sw  0  0<\/code><\/pre>\n\n\n\n
                      To disable swap temporarily (useful before removing a swap file or partition):<\/p>\n\n\n\n
                      sudo swapoff \/swapfile<\/code><\/pre>\n\n\n\n
                      Swap partition vs swap file:<\/strong> Swap partitions have slightly less overhead because the kernel accesses them directly without going through a filesystem layer. Swap files are easier to manage and resize. For most workloads, the performance difference is negligible. Cloud instances and containers typically use swap files when swap is needed at all.<\/p>\n\n\n\n
                      9. Logical Volume Management (LVM)<\/h2>\n\n\n\n
                      LVM adds a layer of abstraction between your physical disks and your filesystems. It lets you resize volumes, span multiple disks, and take snapshots without downtime. LVM is covered under LPIC-1 Objective 104.1 and is heavily tested.<\/p>\n\n\n\n
                      LVM Architecture<\/h3>\n\n\n\n
                      LVM has three layers:<\/p>\n\n\n\n
                        \n
                      • Physical Volumes (PVs)<\/strong> – Raw partitions or whole disks initialized for LVM<\/li>\n
                      • Volume Groups (VGs)<\/strong> – Pools of storage made from one or more PVs<\/li>\n
                      • Logical Volumes (LVs)<\/strong> – Virtual partitions carved from a VG. These are what you format and mount.<\/li>\n<\/ul>\n\n\n\n
                        Creating LVM Volumes<\/h3>\n\n\n\n
                        First, mark the partitions as LVM physical volumes. Make sure the partition type is set to 8e (fdisk) or 8e00 (gdisk) beforehand:<\/p>\n\n\n\n
                        sudo pvcreate \/dev\/sdb1 \/dev\/sdc1<\/code><\/pre>\n\n\n\n
                        Verify your physical volumes:<\/p>\n\n\n\n
                        sudo pvs<\/code><\/pre>\n\n\n\n
                        Create a volume group from these PVs:<\/p>\n\n\n\n
                        sudo vgcreate vg_data \/dev\/sdb1 \/dev\/sdc1<\/code><\/pre>\n\n\n\n
                        Check the volume group:<\/p>\n\n\n\n
                        sudo vgs<\/code><\/pre>\n\n\n\n
                        Create a logical volume. Allocate 50 GiB:<\/p>\n\n\n\n
                        sudo lvcreate -L 50G -n lv_projects vg_data<\/code><\/pre>\n\n\n\n
                        Or allocate all remaining free space:<\/p>\n\n\n\n
                        sudo lvcreate -l 100%FREE -n lv_projects vg_data<\/code><\/pre>\n\n\n\n
                        Note the lowercase -l<\/code> for extents\/percentage vs uppercase -L<\/code> for absolute sizes. The logical volume device path will be \/dev\/vg_data\/lv_projects<\/code> (or equivalently \/dev\/mapper\/vg_data-lv_projects<\/code>).<\/p>\n\n\n\n
                        Now format and mount:<\/p>\n\n\n\n
                        sudo mkfs.ext4 \/dev\/vg_data\/lv_projects\nsudo mkdir -p \/mnt\/projects\nsudo mount \/dev\/vg_data\/lv_projects \/mnt\/projects<\/code><\/pre>\n\n\n\n
                        Extending LVM Volumes<\/h3>\n\n\n\n
                        This is where LVM really pays off. Extend a logical volume by 20 GiB:<\/p>\n\n\n\n
                        sudo lvextend -L +20G \/dev\/vg_data\/lv_projects<\/code><\/pre>\n\n\n\n
                        Then grow the filesystem to fill the new space. For ext4:<\/p>\n\n\n\n
                        sudo resize2fs \/dev\/vg_data\/lv_projects<\/code><\/pre>\n\n\n\n
                        For XFS (which uses a different tool):<\/p>\n\n\n\n
                        sudo xfs_growfs \/mnt\/projects<\/code><\/pre>\n\n\n\n
                        Note that xfs_growfs<\/code> takes the mount point as its argument, not the device path. You can combine the LV extend and filesystem resize in one command:<\/p>\n\n\n\n
                        sudo lvextend -L +20G --resizefs \/dev\/vg_data\/lv_projects<\/code><\/pre>\n\n\n\n
                        The --resizefs<\/code> flag automatically detects the filesystem type and runs the appropriate resize tool.<\/p>\n\n\n\n
                        Reducing LVM Volumes<\/h3>\n\n\n\n
                        Shrinking is more involved and riskier than growing. You must shrink the filesystem first, then shrink the LV. XFS cannot be shrunk at all.<\/p>\n\n\n\n
                        For ext4, unmount the filesystem first, then run a filesystem check, shrink the filesystem, and finally shrink the LV:<\/p>\n\n\n\n
                        sudo umount \/mnt\/projects\nsudo e2fsck -f \/dev\/vg_data\/lv_projects\nsudo resize2fs \/dev\/vg_data\/lv_projects 30G\nsudo lvreduce -L 30G \/dev\/vg_data\/lv_projects<\/code><\/pre>\n\n\n\n
                        Always shrink the filesystem to a size equal to or smaller than the target LV size. If you shrink the LV below the filesystem size, you will destroy data.<\/p>\n\n\n\n
                        LVM Snapshots<\/h3>\n\n\n\n
                        Snapshots capture the state of an LV at a specific moment. They are copy-on-write, so they initially use very little space and grow as the original volume changes.<\/p>\n\n\n\n
                        sudo lvcreate -s -L 5G -n snap_projects \/dev\/vg_data\/lv_projects<\/code><\/pre>\n\n\n\n
                        The -s<\/code> flag marks this as a snapshot. The 5G is the size of the snapshot space (how much change it can track before it fills up and becomes invalid). Mount the snapshot read-only to access the point-in-time copy:<\/p>\n\n\n\n
                        sudo mount -o ro \/dev\/vg_data\/snap_projects \/mnt\/snapshot<\/code><\/pre>\n\n\n\n
                        Remove a snapshot when you are done with it:<\/p>\n\n\n\n
                        sudo lvremove \/dev\/vg_data\/snap_projects<\/code><\/pre>\n\n\n\n
                        If you need to add more physical storage to a volume group later, add a new PV and extend the VG:<\/p>\n\n\n\n
                        sudo pvcreate \/dev\/sdd1\nsudo vgextend vg_data \/dev\/sdd1<\/code><\/pre>\n\n\n\n
                        10. Filesystem Maintenance<\/h2>\n\n\n\n
                        Filesystems need occasional maintenance. Corruption happens, performance degrades, and metadata gets stale. The LPIC exam expects you to know the right tool for each filesystem type.<\/p>\n\n\n\n
                        fsck (Filesystem Check)<\/h3>\n\n\n\n
                        fsck<\/code> is the front-end that calls the appropriate checker for each filesystem type. Never run fsck on a mounted filesystem.<\/strong> Unmount it first, or boot into single-user\/rescue mode.<\/p>\n\n\n\n
                        sudo umount \/dev\/sdb1\nsudo fsck \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        For ext4 specifically, you can use e2fsck<\/code> directly. The -f<\/code> flag forces a check even if the filesystem appears clean:<\/p>\n\n\n\n
                        sudo e2fsck -f \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        Add -p<\/code> to automatically repair safe problems without prompting:<\/p>\n\n\n\n
                        sudo e2fsck -fp \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        tune2fs (ext2\/ext3\/ext4 Tuning)<\/h3>\n\n\n\n
                        tune2fs<\/code> adjusts tunable parameters on ext-family filesystems. Common uses:<\/p>\n\n\n\n
                        View current filesystem parameters:<\/p>\n\n\n\n
                        sudo tune2fs -l \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        Set a filesystem label:<\/p>\n\n\n\n
                        sudo tune2fs -L \"data_vol\" \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        Adjust the reserved block percentage (by default 5% is reserved for root). On a large data volume where root does not need reserved space, reduce it:<\/p>\n\n\n\n
                        sudo tune2fs -m 1 \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        Set the maximum mount count before a forced fsck:<\/p>\n\n\n\n
                        sudo tune2fs -c 30 \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        Set the maximum time interval between filesystem checks:<\/p>\n\n\n\n
                        sudo tune2fs -i 90d \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        dumpe2fs (ext Filesystem Info)<\/h3>\n\n\n\n
                        dumpe2fs<\/code> dumps detailed information about an ext filesystem, including block group details, superblock locations, and feature flags:<\/p>\n\n\n\n
                        sudo dumpe2fs \/dev\/sdb1 | head -50<\/code><\/pre>\n\n\n\n
                        For just the superblock info without the block group details, add -h<\/code>:<\/p>\n\n\n\n
                        sudo dumpe2fs -h \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        xfs_repair<\/h3>\n\n\n\n
                        XFS has its own repair tool. Like fsck, it must be run on an unmounted filesystem:<\/p>\n\n\n\n
                        sudo umount \/mnt\/data\nsudo xfs_repair \/dev\/sdb2<\/code><\/pre>\n\n\n\n
                        If the log is dirty (the filesystem was not cleanly unmounted), xfs_repair will refuse to run. Clear the log first:<\/p>\n\n\n\n
                        sudo xfs_repair -L \/dev\/sdb2<\/code><\/pre>\n\n\n\n
                        The -L<\/code> flag zeroes out the log. This may cause some data loss for transactions that were in the log, but it lets the repair proceed.<\/p>\n\n\n\n
                        To view XFS filesystem information (similar to dumpe2fs for ext):<\/p>\n\n\n\n
                        sudo xfs_info \/mnt\/data<\/code><\/pre>\n\n\n\n
                        11. Disk Usage and Block Device Information<\/h2>\n\n\n\n
                        Monitoring disk usage is a daily task for any sysadmin. The LPIC exam covers several tools for this.<\/p>\n\n\n\n
                        df (Disk Free)<\/h3>\n\n\n\n
                        Show filesystem usage in human-readable format:<\/p>\n\n\n\n
                        df -hT<\/code><\/pre>\n\n\n\n
                        The -h<\/code> flag gives human-readable sizes (G, M, K). The -T<\/code> flag shows the filesystem type. To check a specific mount point:<\/p>\n\n\n\n
                        df -hT \/mnt\/data<\/code><\/pre>\n\n\n\n
                        Show inode usage instead of block usage (useful when you are running out of inodes on ext filesystems with lots of tiny files):<\/p>\n\n\n\n
                        df -i<\/code><\/pre>\n\n\n\n
                        du (Disk Usage)<\/h3>\n\n\n\n
                        While df<\/code> shows overall filesystem usage, du<\/code> tells you which directories are consuming space. Show the total size of a directory:<\/p>\n\n\n\n
                        du -sh \/var\/log<\/code><\/pre>\n\n\n\n
                        Show subdirectory sizes sorted by size (find the space hogs):<\/p>\n\n\n\n
                        du -h --max-depth=1 \/var | sort -hr<\/code><\/pre>\n\n\n\n
                        The -s<\/code> flag summarizes (shows total only), and --max-depth<\/code> controls how many levels deep to report.<\/p>\n\n\n\n
                        lsblk (List Block Devices)<\/h3>\n\n\n\n
                        lsblk<\/code> shows all block devices in a tree view:<\/p>\n\n\n\n
                        lsblk<\/code><\/pre>\n\n\n\n
                        Show additional information like filesystem type, UUID, and size:<\/p>\n\n\n\n
                        lsblk -f<\/code><\/pre>\n\n\n\n
                        The -f<\/code> output includes the filesystem type, label, UUID, available space, and mount point all in one view. This is often faster than running multiple commands.<\/p>\n\n\n\n
                        blkid (Block Device Attributes)<\/h3>\n\n\n\n
                        blkid<\/code> shows UUID, filesystem type, and labels for block devices:<\/p>\n\n\n\n
                        sudo blkid<\/code><\/pre>\n\n\n\n
                        Query a specific device:<\/p>\n\n\n\n
                        sudo blkid \/dev\/sdb1<\/code><\/pre>\n\n\n\n
                        This is the command you will reach for most often when you need a UUID for an fstab entry.<\/p>\n\n\n\n
                        12. LPIC-1 Exam Objectives Mapped<\/h2>\n\n\n\n
                        Here is how everything in this guide maps to the official LPIC-1 (101-500) exam objectives. Use this as a checklist for your study sessions.<\/p>\n\n\n\n
                        102.1 – Design Hard Disk Layout<\/h3>\n\n\n\n