LFCS Storage Management Practice Question
You are managing a Linux server that hosts a critical application using a 500GB ext4 filesystem on an LVM logical volume. The application writes large log files that are rotated weekly. Recently, the system has been experiencing intermittent performance degradation and occasional 'Input/output error' messages when writing to the log directory. The disk (SSD) is relatively new, and SMART tests report no errors. The filesystem is not full, with 60% usage. You notice that the errors occur more frequently during peak write times. Which of the following is the most appropriate first step to diagnose and resolve the issue?
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
✓
Unmount the filesystem and run 'e2fsck -f' to check and repair filesystem corruption.
The correct first step. The symptoms of intermittent I/O errors on a filesystem that is not full and with a healthy SSD suggest filesystem corruption rather than hardware failure. Running 'e2fsck -f' will force a check and repair of the ext4 filesystem, which can resolve the errors. Option A is incorrect because adding an LVM cache layer would only improve performance but not fix corruption. Option C is incorrect because replacing the SSD is not warranted given clean SMART tests. Option D is incorrect because mounting with 'noatime' reduces write overhead but does not address filesystem corruption.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add an LVM cache layer to improve write performance.
Why it's wrong here
This adds complexity and does not address potential corruption.
- ✓
Unmount the filesystem and run 'e2fsck -f' to check and repair filesystem corruption.
Why this is correct
Filesystem corruption can cause I/O errors even if disk is healthy.
- ✗
Replace the SSD immediately as it is likely failing despite SMART tests.
Why it's wrong here
SMART shows no errors, so replacement is premature.
- ✗
Mount the filesystem with the 'noatime' option to reduce write overhead.
Why it's wrong here
This may reduce writes but won't fix existing I/O errors.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 507 original LFCS practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This LFCS practice question is part of Courseiva's free Linux Foundation 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 LFCS exam.