Umount directory

[O'lnes]

When I run umount a directory, it pop up 'Device busy' , but I make sure no process in the directory and no user on the directory, how to run umount? Thanks.

[Justo Exposito]

Hi,

You can use fuser command or look for the lsof tool in internet in order to know the process that locks the file system.

Regards,

Justo.

[Dietmar Konermann]

Hi!

Besides running processes (see fuser/lsof) there are some more things that may keep an file system busy, e.g.:

- active fs swap
- other fs mounted into it

If the fs is NFS exported then an NFS client lock may also be able to make trouble. You then need to restart rpc.lockd and rpc.statd... then the umount should work.

Regards...
Dietmar.

[James R. Ferguson]

Hi:

A very common reason for not being able to unmount a filesystem is that you or someone else is CD'ed into the directory.

Regards!

...JRF...

[Craig Rants]

NFS was mentioned, attached is a link for troubleshooting nfs problems, but it also useful for troubleshooting device busy problems as well.

http://docs.hp.com/hpux/onlinedocs/B1031-90048/00/00/42-con.html

GL,
C

[Ray Brewer · Accepted solution]

One thing Dietmar mentioned gets me all the time filesystem mounted on a filesystemsuch as this
/dir1
/dir1/dir2
The first filesystem, /dir1, can not be unmounted until /dir1/dir2 has been unmounted.

Ray

[Sean OB_1]

umount won't unmount a file system if it is in use.

This could mean there are apps actively accessing the files. Or it could be as simple as a shell account being in that directory.

The first thing to do is cd to / to make sure you aren't the one keeping the device busy. :-)

Then if that doesn't work issue:

fuser -c /file/system/to/unmount
fuser -u /file/system/to/unmount

This will tell you what processes are using the file system. Check each process to make sure you know what it is and shutdown the process.

Once no processes are using the file system you will be able to unmount it.

Sean

[MANOJ SRIVASTAVA]

Hi


fuser -ck /mountpoint; umount /mount point , this should do the work , incase there are processes associated they will get killed . You can also try lsof to find out what are the open files accociated with the mount point.


Manoj Srivastava