LPI Exam 101-500 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?

AThe kernel has not finished flushing disk writes to themounted device.

BA user has a file open in the /mnt directory.

CAnother file system still contains a symlink to a file inside /mnt.

DThe files in /mnt have been scanned and added to the locate database.

EThe kernel thinks that a process is about toopen a file in /mnt for reading.

Show Suggested 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:

Submit Cancel

Lemuel

1 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

Adela

12 days ago

B) A user has a file open in the /mnt directory.

upvoted 0 times

...

Celestine

17 days ago

A) The kernel has not finished flushing disk writes to the mounted device.

upvoted 0 times

...

Nobuko

1 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

1 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

...

Lillian

2 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

1 months ago

C) Another file system still contains a symlink to a file inside /mnt.

upvoted 0 times

...

Lettie

1 months ago

B) A user has a file open in the /mnt directory.

upvoted 0 times

...

Ryann

1 months ago

A) The kernel has not finished flushing disk writes to the mounted device.

upvoted 0 times

...

Frank

2 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

2 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