EX200 Configure local storage Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  lvcreate -n data -L 3G vg01

  Why this is correct

  This command correctly creates a new logical volume named 'data' with a size of 3GiB (using the -L option, where 'G' denotes GiB) within volume group vg01. Since vg01 has 5GiB of free space, the allocation request is satisfied and the LV is created successfully with default linear mapping. The -n flag assigns the name, and the final positional argument correctly specifies the volume group, which is the only valid target for lvcreate.

• ✗

  lvcreate -n data -L 3G vg00

  Why it's wrong here

  This command fails because vg00 has only 2GiB of free space, while the -L 3G option requests a 3GiB logical volume. LVM will reject the operation with an 'Insufficient free space' error before creating the LV, as the allocation cannot be fulfilled. Even though vg00 exists and is a valid volume group, its available capacity is the binding constraint, so the command is not merely undersized but outright invalid in this situation.

• ✗

  lvcreate -n data -L 3G /dev/sda1

  Why it's wrong here

  This command is invalid because /dev/sda1 is a physical volume (or partition), not a volume group, and lvcreate's positional argument must be an existing volume group name. Passing /dev/sda1 as the last argument makes LVM attempt to interpret it as a VG name, which does not exist, resulting in a 'Volume group /dev/sda1 not found' error. The -L and -n options are fine, but the target must be a VG such as vg01 or vg00, never a block device path.

• ✗

  lvcreate -n data -l 100 vg01

  Why it's wrong here

  This command incorrectly uses the -l flag, which counts extents rather than a human-readable size; with a default physical extent size of 4MiB, 100 extents only allocate 400MiB (0.4GiB), far short of the required 3GiB. Although vg01 has enough free space for 100 extents, the resulting logical volume would be named 'data' but sized at 400MiB, not 3GiB. To create a 3GiB LV, the administrator must either use -L 3G or specify -l 768 (since 3GiB / 4MiB = 768 extents).

• ✗

  lvcreate -n data -l 100 vg00

  Why it's wrong here

  This command is doubly wrong: it targets vg00, which has only 2GiB of free space, and it uses -l 100 to request just 100 extents, which at 4MiB per extent equals only 400MiB. The command would technically succeed in vg00 because 400MiB fits within the 2GiB free space, but it creates a 400MiB LV named 'data' instead of the intended 3GiB LV. Both the volume group choice and the extent-based size specification are incorrect for the stated requirement of a 3GiB logical volume.

Go deeper

Related to this question