topic Re: pfs_mount in Operating System - HP-UX

pfs_mount

Sylvie Vezina — Mon, 30 Apr 2001 16:03:14 GMT

we used pfs_mount for using CDROM on L1000 Unix 11.0 and we're not able to perform an umount. We have to reboot system!!! When we tried pfs_umount, the system said "device busy".

Re: pfs_mount

Michael Elleby III — Mon, 30 Apr 2001 16:06:24 GMT

Well, of course some common things come to mind:

1 - Were you and anybody else out of the directory? - confirm this with an fuser command on the file system to see if there are any users..

2 - Any user that was using the file system, have them log out of the system entirely..

From outside the filesystem directory, try the unmount again...

Mike

Re: pfs_mount

A. Clay Stephenson — Mon, 30 Apr 2001 16:12:39 GMT

Do an fuser -c /cdrom (or wahatever the mount directory is)
you should see a list of processes (pids) which are using the cdrom. ps -p pid -f will then give you more information.

Re: pfs_mount

Joseph C. Denman — Mon, 30 Apr 2001 16:18:24 GMT

Agree with Clay...

I says device is busy because....device is busy. Use fuser to determine which process has a hold on the mountpoint. Then kill the process.

...jcd...

Re: pfs_mount

Michael Elleby III — Mon, 30 Apr 2001 16:21:42 GMT

Maybe I should have clarified my answer a little better for jcd...

When I stated about the fuser, do it first to see if there is a process/user that has a hold on it, then use the -k parameter to kill the process..

Then log that user out.. I have had similar problems with Oracle CD's..

Mike

Re: pfs_mount

MANOJ SRIVASTAVA — Mon, 30 Apr 2001 16:28:27 GMT

I Think your problem is that even if you are able to unmount you cant eject the CDROM . Incase you are not using pfs_umount or there are remanent pfs processes then the CD will not be able to eject . So do the following :

1. pfs_umount ( obviously nobody should be in thtat directory , user fuser -c < mount directory > to know who is using it .

2. Incase you cant eject th
e CD out try this do ps -ef | grep pfs and kill the processes in the incresing order ,

that means issue kill -9 to the lowest id and then go ahead . After that is done th CD will be able to come out.

Also in the later version of ORACLE 8.1.7 there are two CD to be used in while installing oracle . Incase you are stuck up after the first CD then in the oracle install GUi go to the root directory this will free the mount point being owned by oracle.

This should work for you.

Manoj

Re: pfs_mount

James R. Ferguson — Mon, 30 Apr 2001 17:41:48 GMT

Hi:

A word of caution (from bitter experience, too!):

The order in which you start a 'pfs_mount' process is stictly reversed when you unmount.

First, make sure that you *only* use 'pfs_umount'. Do *not* use the standard 'umount' command. Remember to 'cd' "out" of the mounted directory first.

Next, kill the 'pfsd' daemon, and *then* lastly, the 'pfs_mountd' daemon.

Failure to observe this order can lead to a "hung" system, most notably one where queries of filesystems and directories "hang" and processor utilization climbs and climbs, leading to a reboot to ressurrect an unresponsive system.

...JRF...

Re: pfs_mount

MANOJ SRIVASTAVA — Mon, 30 Apr 2001 17:51:12 GMT

I agree with James , ie is why I said that you have to kill the process in the ascending order first the lower id then go up.

Manoj

Re: pfs_mount

Shaun Walter — Mon, 30 Apr 2001 18:04:04 GMT

I agree completely with James. This is the progression you must follow when using pfs_mount'd media (ORACLE CDs).

You also may want to consider creating a seperate mount point just for PFS mounted media. This will help you remember NEVER to do a umount for these. Use the seperate mount point (/PFSCD) for pfs_mounted media and then remember to do a pfs_umount AFTER changing to the root directory and running fuser -c /PFSCD to check that nobody is still in.

Hope this helps

Re: pfs_mount

Rajeev Tyagi — Wed, 02 May 2001 13:11:17 GMT

Sylvie,

Why dont you try fuser on device file rather than mount point.
Next thing while doing pfsmount make sure that statd and lockd daemons are running.