XK0-006 Troubleshooting Practice Question
A Linux server's root filesystem was extended with LVM, but after a reboot users report that only the original capacity is available again. Running 'df -h' shows the mount smaller than the logical volume, and 'lvextend' completed successfully before the reboot. Which command should the administrator run to make the filesystem use the additional space on an XFS root volume?
⚠ Common exam trap
The trap here is assuming that any Linux filesystem can be enlarged with resize2fs, when that utility is limited to the ext family and silently fails on XFS.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
xfs_growfs /
XFS filesystems must be grown with xfs_growfs rather than resize2fs, and the operation can be performed online on a mounted root filesystem. Since lvextend already expanded the logical volume, the remaining step is to tell XFS to claim the new space by pointing xfs_growfs at the mount point. Without this step the filesystem keeps its original size even though the block device is larger.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
resize2fs /dev/mapper/vg0-root
Why it's wrong here
resize2fs only operates on ext2, ext3, and ext4 filesystems. If the root volume is XFS, this command will fail with an error about a bad magic number or unsupported filesystem. It would be the right choice for an ext4 root, but it cannot grow XFS, so it does not solve this scenario.
- ✓
xfs_growfs /
Why this is correct
xfs_growfs expands an XFS filesystem online to fill its underlying block device. Because the logical volume was already enlarged with lvextend, running xfs_growfs against the mount point '/' resizes the filesystem to consume the new extents. This is the correct tool for XFS, which cannot be grown with resize2fs, and it works while the root filesystem is mounted.
- ✗
parted /dev/sda resizepart 2 100%
Why it's wrong here
parted resizepart changes a partition boundary on the disk, not a filesystem inside an LVM logical volume. Since the space was added through LVM rather than by enlarging a physical partition, this command targets the wrong layer and will not extend the mounted XFS filesystem that is already backed by the enlarged logical volume.
- ✗
vgchange -ay vg0
Why it's wrong here
vgchange -ay activates logical volumes in a volume group so they become available to the kernel. It does not resize any filesystem and does not allocate free extents. The volume group is already active because the root filesystem is mounted and in use, so this command changes nothing about the reported capacity.
Go deeper
Related to this question
Learn chapter
Logical Volume Management (LVM)
Key term
lvextend
lvextend is a Linux command used to increase the size of an existing Logical Volume in LVM (Logical Volume Manager) without disrupting the data or the system.
Key term
Linux
Linux is an open-source operating system that manages computer hardware and software, widely used in servers, desktops, and embedded systems.
About these practice questions
This XK0-006 question is part of Courseiva's 781-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This XK0-006 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the XK0-006 exam.