remove cd w/o rebooting

[Ricky_4]

Hi All,

How do I remove my CD without rebooting when my connection suddenly disconnect from remote workstation? By the way I used pfsd, pfs_mountd and pfs_mount to mount my Oracle CD and prompts me device busy when I used pfs_umount.

Thanks

[Thierry Poels_1]

hi,

you did cd away from the mountpoint before trying to pfs_umount??
Use lsof or fuser to find out which process is still running on this mountpoint. Stop/kill it and try pfs_umount again.

good luck,
Thierry.

[Sanjay_6]

Hi Bal,

Do "fuser -u /mount_point"
This will show the list of process ID's and usernames of everyone using the mounted directory.
Warn users to cd out of the directory, and kill any process that are using the directory. You can use this command to kill all processes using the directory
fuser -ck /mount_point
then unmount the directory or CD
umount /mount_point
Then kill the processes related to pfs_* like pfs_mountd, pfsd, rpc.pfs* and all the processes related to pfs.

If this doesn't solve your problem, then there is no choice rather than rebooting the box.

Hope this helps.

Thanks

[Sharon Prothero]

I had a similar problem after loading Oracle 8.1.6, and for reasons I haven't yet discovered (if any one does know, please tell me) the initital listener it starts to go with the starter database has some kind of lock on the cd mount.

I ran the fuser command on the cd mount
# fuser node:/cdrom
then ran a ps on the process number returned. The process number belonged to the Oracle listener & the letter c at the end of the return from fuser indicated that the process was using the cd as its current directory.

If you do have this problem you can run the Oracle lsnrctl utility to stop & restart the listener & remove the lock from the cd mount.

BUT BEWARE, I now have problems getting the ORA-12547 error when I try to connect to the database. I believe that this is related to a patching issue which I'm currently fixing, but I though I ought to warn you just in case it's anything to do with the listener.

HTH
Sharon

[John Waller]

Bal, Like Sharon , I also have seen the problem after an ORACLE install where the listener seems to have a lock on the /cdrom . The only reason I can think of is that the ORACLE install script performs a cd to /cdrom/??? at some point before it auto starts the listener, and the listener process somehow locks itself to the pwd. A "fuser -c /cdrom" showed the offending PID, once killed the cdron could unmount with the pfs_umount command.