- A
Restart the MySQL service with 'systemctl restart mysql'.
Restarting MySQL closes all open file handles, allowing the kernel to release the disk space occupied by deleted files.
- B
Use 'dpkg --purge mysql-server' to completely remove MySQL, then reinstall it.
Why wrong: This is drastic and unnecessary; you just need to restart MySQL to release file handles.
- C
Run 'e2fsck -f /dev/sda3' to reclaim inodes and fix filesystem inconsistencies.
Why wrong: e2fsck will check the filesystem but cannot close open file handles; space is still consumed.
- D
Move the binary logs to a different partition using 'mv /var/lib/mysql/mysql-bin.* /tmp/' and then delete them.
Why wrong: The files were already deleted; mv will fail. The issue is open handles.
LPIC-1 Devices, Filesystems and FHS Practice Question
This LPIC-1 practice question tests your understanding of devices, filesystems and fhs. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are a system administrator at a hosting company. A customer reports that their website hosted on a shared LAMP server is returning error 500. The server runs Ubuntu 22.04 with Apache, MySQL, and PHP. You log in and find that the /var partition (on /dev/sda3, ext4) is almost full. You identify that the MySQL database directory /var/lib/mysql contains several large binary logs that are no longer needed. You delete the binary logs using 'rm -f /var/lib/mysql/mysql-bin.*'. However, the available space does not increase. You also notice that an inode leak is suspected. You check inode usage with 'df -i' and see that the partition has plenty of free inodes. You then check with 'lsof | grep deleted' and see several entries for mysqld holding deleted files. What is the correct procedure to free the space?
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
Restart the MySQL service with 'systemctl restart mysql'.
When a file is deleted while a process (like mysqld) still holds an open file descriptor to it, the file's inode remains allocated and the disk space is not freed until the process releases the descriptor. Restarting the MySQL service (systemctl restart mysql) causes mysqld to close all open file descriptors, allowing the kernel to release the deleted binary logs' inodes and reclaim the disk space.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Restart the MySQL service with 'systemctl restart mysql'.
Why this is correct
Restarting MySQL closes all open file handles, allowing the kernel to release the disk space occupied by deleted files.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use 'dpkg --purge mysql-server' to completely remove MySQL, then reinstall it.
Why it's wrong here
This is drastic and unnecessary; you just need to restart MySQL to release file handles.
- ✗
Run 'e2fsck -f /dev/sda3' to reclaim inodes and fix filesystem inconsistencies.
Why it's wrong here
e2fsck will check the filesystem but cannot close open file handles; space is still consumed.
- ✗
Move the binary logs to a different partition using 'mv /var/lib/mysql/mysql-bin.* /tmp/' and then delete them.
Why it's wrong here
The files were already deleted; mv will fail. The issue is open handles.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume deleting a file immediately frees disk space, overlooking that processes with open file descriptors prevent the kernel from releasing the inode and data blocks until the descriptor is closed.
Detailed technical explanation
How to think about this question
Under Linux, when a file is deleted but still open, the kernel keeps the inode and data blocks allocated until the last file descriptor is closed. The 'lsof | grep deleted' command reveals such files. This behavior is critical in database environments where large log files (e.g., MySQL binary logs) are often rotated or deleted while the database is running; simply deleting them without restarting the service or using the MySQL PURGE BINARY LOGS command leaves space unreclaimed.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the LPIC-1 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Devices, Filesystems and FHS — study guide chapter
Learn the concepts, then practise the questions
- →
Devices, Filesystems and FHS practice questions
Targeted practice on this topic area only
- →
All LPIC-1 questions
522 questions across all exam domains
- →
Linux Professional Institute Certification Level 1 LPIC-1 study guide
Full concept coverage aligned to exam objectives
- →
LPIC-1 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related LPIC-1 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
GNU and Unix Commands practice questions
Practise LPIC-1 questions linked to GNU and Unix Commands.
Devices, Filesystems and FHS practice questions
Practise LPIC-1 questions linked to Devices, Filesystems and FHS.
Linux Installation and Package Management practice questions
Practise LPIC-1 questions linked to Linux Installation and Package Management.
Essential System Services and Networking practice questions
Practise LPIC-1 questions linked to Essential System Services and Networking.
Administrative Tasks practice questions
Practise LPIC-1 questions linked to Administrative Tasks.
Shells, Scripting and Data Management practice questions
Practise LPIC-1 questions linked to Shells, Scripting and Data Management.
System Architecture practice questions
Practise LPIC-1 questions linked to System Architecture.
LPIC-1 fundamentals practice questions
Practise LPIC-1 questions linked to LPIC-1 fundamentals.
LPIC-1 scenario practice questions
Practise LPIC-1 questions linked to LPIC-1 scenario.
LPIC-1 troubleshooting practice questions
Practise LPIC-1 questions linked to LPIC-1 troubleshooting.
Practice this exam
Start a free LPIC-1 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this LPIC-1 question test?
Devices, Filesystems and FHS — This question tests Devices, Filesystems and FHS — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Restart the MySQL service with 'systemctl restart mysql'. — When a file is deleted while a process (like mysqld) still holds an open file descriptor to it, the file's inode remains allocated and the disk space is not freed until the process releases the descriptor. Restarting the MySQL service (systemctl restart mysql) causes mysqld to close all open file descriptors, allowing the kernel to release the deleted binary logs' inodes and reclaim the disk space.
What should I do if I get this LPIC-1 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 25, 2026
This LPIC-1 practice question is part of Courseiva's free LPI 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 LPIC-1 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.