I've mounted a block device (internal hard disk) to say ~/HD, and I'm trying,

~# umount ~/HD

It answers,

umount: device is busy.

Now I kill all processes manually by examining

~# fuser -m ~/HD

I also make sure that really no process is accessing the ~/HD path

~# lsof | grep HD

Still umount ~/HD says device is busy even with -f option.

PS: I don't want to use the -l option of umount, since the mounted device is actually an encrypted mapper device, which in turn won't get unmounted unless mapper device is clearly unmounted.

So basically my question is how to really force umount to unmount a device OR How can a device still be marked as busy while no processes are accessing it (or at least fuser and lsof don't report it) and what can I do about it?

I'm on Ubuntu 9.10 x64.

1

8 Answers

You will see this behavior if you have mounted something else on a subdirectory of ~/hd. In this case, neither fuser nor lsof will show anything. If you haven't mounted anything under ~/hd ('mount' will answer this question), then I'm not sure what to check.

1

Make sure your current working directory (run 'pwd') is not a under ~/hd. If you are currently in that directory, umount will refuse to unmount.

Command lsof will tell you what process(es) hold a file open.

to locate active processes/users execute:

fuser -u /path/to/mount

then execute the following to remove them:

fuser -k /path/to/mount

finally umount the offending device.

1

Larsks wrote: "You will see this behavior if you have mounted something else on a subdirectory of ~/hd. In this case, neither fuser nor lsof will show anything."

Using lsof with grep will show subdirectory use - eg "lsof |grep HD".

I had the same problem as the original poster and found the cause using the command above.

Have you tried to use sync?

The sync command flush the filesystem caches by force the changed blocks to be writed on the disk.

1

If you really want to just unmount it, you can use umount -f

from man umount :

-f Force unmount (in case of an unreachable NFS system). (Requires kernel 2.1.116 or later.)

1

I couldn't unmount because a user had an open SMB session. Worth checking.

6

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy