What process is keeping my CD busy?

[Terrence Johnson]

This should be simple enough. I have a CD in the drive and it's mounted to /cdrom. I want to umount it but I get the message: "cannot umount /cdrom : Device busy".
Usually that means that I'm still in the /cdrom directory and all I have to do is cd / to release it. This time though, it's not me and I can't see a single other user who would even know the CD is on the system. Short of rebooting the server, how can I kill the process that's blocking me from umount(ing) the CD?

[Steve Labar]

You can try doing an fuser -u /cdrom to see what/who is using it. Or you could do an fuser -ku /cdrom which will kill any process that is using it.

Good Luck.

Steve

[Ken Hubnik_2]

fuser -c /cdrom

will show the processes that are accessing that mount point.

[Terrence Johnson]

Nope. The fuser -u comes back blank, as does the fuser -ku and the problem remains. I wonder if I have a zombie?

[Pete Randall]

Terrence,

You should check into lsof - a very handy utility. You can find a couple of sources for it in this thread:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xf58885079106d71190050090279cd0f9,00.html


Pete

[Paul Sperry]

Checkout lsof:

http://www.mirrors.wiretapped.net/security/host-security/lsof/binaries/hpux/B.11.11/

[Steven E. Protter]

I you just want to umount


fuser -cuk /cdrom

or whatever you call the cd.

As sysadmin, don't be surprised if this command kills your telnet session.

About half the time I get the error message, I've got a session on the cdrom.

P

[pap]

Hi,
Just do fuser -c /cdrom

You will see the processes using cdrom drive. Otherwise just do following and you will be able to unmount the cd drive.

# fuser -ck /cdrom
#umount /cdrom

Hope this will help.

-pap

[Bill Hassell]

fuser often fails because it looks for open files relative to the /cdrom path. Always run fuser against the device file as in:

fuser /dev/dsk/c0t2d0

(or whatever your CDROM device file might be) The problem is usually caused by user cd'ing into the CDROM. They haven't opened a file like you would running vi or cat but nevertheless, the directory /cdrom (and perhaps subdirectories underneath) are indeed open, but in a different way.

fuser is only about 75% effective in finding the reason for umount failures. Get a copy of lsof from http://hpux.connect.org.uk/