Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

LPI 101-500 Exam - Topic 4 Question 88 Discussion

Actual exam question for LPI's 101-500 exam
Question #: 88
Topic #: 4
[All 101-500 Questions]

After running the command umount /mnt, the following error message is displayed:

umount: /mnt: device is busy.

What is a common reason for this message?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Coral at May 24, 2024, 03:51 AM

Limited Time Offer

25%

Off

Get Premium 101-500 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Phil
4 months ago
The kernel flushing writes is also a possibility, but less common.
upvoted 0 times
...
Valentin
4 months ago
Wait, really? I didn't know that could happen!
upvoted 0 times
...
Valentin
4 months ago
I thought it could be a symlink issue too.
upvoted 0 times
...
Dahlia
4 months ago
Totally agree, that's usually it!
upvoted 0 times
...
Leonora
4 months ago
Common reason? A user has a file open in /mnt.
upvoted 0 times
...
Micah
5 months ago
I vaguely recall something about processes and the kernel thinking a file is about to be opened. E sounds familiar, but I’m not confident.
upvoted 0 times
...
Elfrieda
5 months ago
I practiced a similar question where a symlink caused issues. Could it be C? I feel like that might be a possibility.
upvoted 0 times
...
Shaniqua
5 months ago
I think the kernel flushing writes could be a reason too, but that seems less likely than a user having a file open.
upvoted 0 times
...
Tamesha
5 months ago
I remember something about processes holding onto files, so maybe it's B? But I'm not completely sure.
upvoted 0 times
...
Precious
5 months ago
This is a classic Linux systems administration question. I'm pretty confident I know the common reasons for a "device is busy" error when trying to unmount. I'll quickly review the options and select the most likely answer.
upvoted 0 times
...
Jonelle
5 months ago
Okay, I've got a strategy for this. The key is to think about what could be holding a reference to the mounted device, preventing it from being unmounted. I'll carefully consider each option and try to eliminate the less likely ones.
upvoted 0 times
...
Eric
5 months ago
Hmm, I'm a bit unsure about this one. The error message doesn't give me a lot of context, so I'll have to think through the possible reasons why the device could be busy. I'll make sure to read the options closely.
upvoted 0 times
...
Elza
5 months ago
This seems like a pretty straightforward question. I'll carefully read through the options and think about common reasons why a device might be busy when trying to unmount it.
upvoted 0 times
...
Apolonia
6 months ago
I'm a bit confused by the options here. I'll need to think through the different ways to approach a layout change like this.
upvoted 0 times
...
Tijuana
6 months ago
I'm a little confused by this question. Scoping to host names doesn't seem relevant, since we're targeting specific containers. I'm leaning towards option B, scoping to namespaces, but I'm not 100% sure.
upvoted 0 times
...
Lemuel
10 months ago
I bet the person who wrote this question was chuckling to themselves the whole time, trying to come up with the most absurd options possible.
upvoted 0 times
Tamar
9 months ago
C) Another file system still contains a symlink to a file inside /mnt.
upvoted 0 times
...
Adela
9 months ago
B) A user has a file open in the /mnt directory.
upvoted 0 times
...
Celestine
10 months ago
A) The kernel has not finished flushing disk writes to the mounted device.
upvoted 0 times
...
...
Nobuko
10 months ago
The kernel thinking a process is about to open a file in /mnt for reading? That's got to be the silliest reason I've Nobukor heard for this error message.
upvoted 0 times
...
Heike
10 months ago
The files in /mnt being added to the locate database? That's a new one for me. I wonder if the exam writers are just trying to trick us with that one.
upvoted 0 times
Mitsue
9 months ago
C) Another file system still contains a symlink to a file inside /mnt.
upvoted 0 times
...
Dortha
9 months ago
B) A user has a file open in the /mnt directory.
upvoted 0 times
...
Jospeh
9 months ago
A) The kernel has not finished flushing disk writes to the mounted device.
upvoted 0 times
...
...
Lillian
11 months ago
Another file system with a symlink to a file inside /mnt? That's an interesting possibility, but it doesn't seem as common as the first two options.
upvoted 0 times
Aliza
10 months ago
C) Another file system still contains a symlink to a file inside /mnt.
upvoted 0 times
...
Lettie
10 months ago
B) A user has a file open in the /mnt directory.
upvoted 0 times
...
Ryann
10 months ago
A) The kernel has not finished flushing disk writes to the mounted device.
upvoted 0 times
...
...
Frank
11 months ago
Hmm, a user having a file open in the /mnt directory makes sense too. I need to be more careful about that when working with mounted file systems.
upvoted 0 times
...
Lynna
11 months ago
The kernel not having finished flushing disk writes sounds like the most likely reason to me. I've encountered this issue before when trying to unmount a busy device.
upvoted 0 times
Thomasena
9 months ago
That makes sense. The kernel could be waiting for that process to finish before unmounting.
upvoted 0 times
...
Tegan
10 months ago
A user likely has a file open in the /mnt directory.
upvoted 0 times
...
Lai
10 months ago
E
upvoted 0 times
...
Jeffrey
10 months ago
A
upvoted 0 times
...
...
Olga
11 months ago
I'm not sure, but I think it could also be E) The kernel thinks that a process is about to open a file in /mnt for reading.
upvoted 0 times
...
Alisha
11 months ago
I agree with Glennis, it makes sense that the device is busy because a file is open in /mnt.
upvoted 0 times
...
Glennis
11 months ago
I think the answer is B) A user has a file open in the /mnt directory.
upvoted 0 times
...

Save Cancel