Exercise 1: Building One Filesystem Larger Than Either Disk — Possible Solution
====================================================================

Command sequence:

pvcreate /dev/sdb
pvcreate /dev/sdc
vgcreate bigvg /dev/sdb /dev/sdc
lvcreate -L 100%FREE -n biglv bigvg
mkfs.ext4 /dev/bigvg/biglv
mount /dev/bigvg/biglv /mnt/data

Explanation:

Per the chapter's own PV/VG/LV model, each disk first needs to be
initialized as a physical volume individually -- pvcreate /dev/sdb and
pvcreate /dev/sdc turn each raw disk into something LVM can use.

The key step for this specific requirement is the volume group:
"vgcreate bigvg /dev/sdb /dev/sdc" combines BOTH physical volumes into
a single pool. Per the chapter, "a volume group can span multiple
physical disks" -- this is exactly what makes it possible for a single
logical volume afterward to be larger than either individual disk,
since the volume group's own total capacity is the sum of every
physical volume added to it, not limited to whichever single disk is
largest.

With both disks combined into one volume group, "lvcreate -L 100%FREE
-n biglv bigvg" carves out a single logical volume using all of the
combined space across both disks (using LVM's percentage-of-free-space
option here rather than a fixed size, though a fixed size like -L 3T
would work identically as long as it fits within the VG's combined
capacity). This logical volume's own size is not constrained by either
individual disk's size -- only by the total space available in the
volume group it was created from.

Finally, mkfs.ext4 and mount work exactly as they would against any
other logical volume, per the chapter's own basic example, since a
logical volume presents itself to the rest of the system as an
ordinary block device regardless of how many physical disks actually
back it.

WHY THIS WORKS AS AN ANSWER
------------------------------
This uses the volume-group step specifically (combining two PVs
before creating the LV) as the mechanism that makes a larger-than-any-
single-disk filesystem possible, rather than skipping straight to a
logical volume creation without explaining why two disks needed to be
combined first.