device busy when mounting CDROM

[Chris Fadrowski]

I keep getting device busy when mounting cdrom. i have all the right patches such as PHKL_27224 installed etc.. I did an fuser and no one is using this device, no PFS daemons are running, so i rm the /cdrom and recreated it and also ran insf -e, yet i am still getting this message. any ideas? i could reboot and it would probably work, but i want to avoid that if possible.

[Jeff Schussele]

Hi Chris,

Do a
showmount -e
and a
showmount -a

May be that is was exported at some time & never unexported.

HTH,
Jeff

[Chris Fadrowski]

showmount: host: RPC: Program not registered


this is all i get running that.

[Jeff Schussele]

Hi Chris,

Next thing I'd do is run lsof against device & mount point. fuser isn't 100% reliable in my book, but lsof has never let me down.

HTH,
Jeff

[Helen French]

1) Does the CDROM shows properly on ioscan:

# ioscan -fnC disk
2) Run a diskinfo and see what is returns:
# diskinfo -v /dev/rdsk/cxtydz

Also, which OS version are you running?

[Chris Fadrowski]

ioscan shows it as claimed.

diskinfo show this

diskinfo: can't open /dev/dsk/c3t2d0: Device busy

lsof does not exist on my system. this is a d class server running HPUX 11.0

[Helen French]

1) Install this patch or it's supercede: PHKL_24282

2) Try removing and recreating /dev/rdsk and /dev/dsk device files on CDROM (rmsf and insf command)

[Chris Fadrowski]

all the patches have been installed previously. There is a superseded patch that has been installed. I did the rmsf -a /dev/rdsk/c3t2d0 and got rid of the file, then insf -e and it returned, still no luck. i tried to do this thru SAM and got this as well.

The command used to mount the new file system, mount(1m), has failed. xtedx
xqqx The stderr output from the command is shown below. The disk has not xqqqx
x x been configured for use. x x
x x x x
xlqx xqk x
xx x The command used to mount the new file system, mount(1m), has failed x ^ x
xx x to mount /cdrom. The stderr output from the command is shown below. x x
xx x x x
xx x /dev/dsk/c3t2d0: Device busy x x
xx x

[Helen French]

Just some silly questions:

1) Do you have a working CDROM on the drive?
2) Create another directory (mkdir /cdtest) and try mounting there.
3) Check ps -ef command output for any process that holds CD drive
4) Since you are using a D class, check and see the SE SCSI connection on your back of the server is properly terminated.
5) Download and install lsof from HP porting center which will help you list any process that holds the drive.

[Chris Fadrowski]

yes the CDROM works, used it last week.
Tried the cdtest directory, didn't work
checked the connections, they seem to be ok, it's showing up as claimed in ioscan

i just installed lsof and did a ./lsof | lp and nothing is showing using the CDROM.

[Mark Grant]

When you used it last week, you didn't happen to do a pfs_mount did you?

If you did you need to force it to unmount which I think is "pfs_umount -c /cdrom"

[Chris Fadrowski]

no i did not. IN fact i have the pfs_mount patches installed. I only mounted a hp cd last week to browse for some software.

can anyone tell me how to use lsof to find if my cdrom is being used? never used it before.

[Jeff Schussele]

Hi Chris,

Here's where you can get it...

http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.67/

Here's the man page....

http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.67/man.html

Basically your command would be like...

lsof /dev/dsk/cXtYdZ

or

lsof /cdrom

HTH,
Jeff

[Chris Fadrowski]

that didn't work i think it's

./lsof -f /cdrom

i am using 4.68 that i just installed 64bit

[Jeff Schussele]

Yep - either way..
f is kinda implicit, after all it does stand for list(ls) open (o) FILES (f).

Anyway, find anything?

Jeff

[Sanjay_6]

Hi Chris,

Remove the device files before trying to recreate them using insf -e.

Hope this helps.

Regds

[Chris Fadrowski]

okay, nothing was going after my cdrom. I am going to reboot the system and see what happens.


You guys have been a great help. thank you.

[leyearn]

to Chris Fadrowski

after you reboot your system
did your problem have been solved?