pfs_mount

[castro_2]

I have problem with pfs_mount, When I do
pfs_umount /cdrom

NFS server sarsubo1 not responding still trying

I don´t want to reboot the system.

Thank

[Steven E. Protter]

You may have to reboot your system.

ps -ef | grep pfs

kill every process that shows up, maybe you will escape the boot monster.

Next time use the script I'm attaching instead of pfs_mount

SEP

[castro_2]

ps -ef|grep pfs
root 24249 23909 1 12:12:16 pts/9 0:00 grep pfs
root 20219 1 0 11:36:18 ? 0:00 pfs_umount /cdrom
root 18817 1 0 11:25:44 ? 0:00 pfs_mountd.rpc
kill -9 20219
ps -ef|grep pfs
root 20219 1 0 11:36:18 ? 0:00 pfs_umount /cdrom
root 24262 23909 1 12:12:24 pts/9 0:00 grep pfs
root 18817 1 0 11:25:44 ? 0:00 pfs_mountd.rpc

The process 20219 don´t die

Than

[Sanjay_6]

Hi Castro,

this is the problem with pfs_mount. If you run into some NFS related issue with pfs_mount, there is no other choice than to reboot.

To avoid this issue from hapening in future, you can load the rock-ridge extention patches for cdrom. These patches would help you to mount the oracle (pfs_mount requiring) cdrom to be mounted using the normal mount command and eliminates the need of pfs_mount.

The patches required are,

for 11.0

PHCO_26449 Add Rock Ridge extension to mount_cdfs
PHKL_28060 Y2k; Rock Ridge extension for ISO-9660
PHKL_26450 Rock Ridge extension for ISO-9660

for 11.11

PHCO_25841 s700_800 11.11 Add Rock Ridge extension to mount_cdfs(1M)
PHKL_26269 Rock Ridge extension for ISO-9660
PHKL_28025 Rock Ridge extension for ISO-9660

There are no patches for 10.20.

Hope this helps.

Regds

[Mic V.]

I agree, you're probably going to have to reboot.

I haven't personally tried the suggested patches -- maybe they will remove all trouble (wouldn't that be nice), but here's what I used to do to avoid trouble (I think I'm remembering them in the right order; if not, just swap and it'll be correct):

1. start pfs_mountd
2. start pfsd
3. pfs_mount and then do whatever is needed with this CD
4. ps ef|grep pfs
5. using the PID (not PPID :), kill the daemons (there are 4 processes all told) from latest child to earliest child. This normally means that of these four, kill the highest numbered first, then the next highest, and so on -- but if your system happens to roll over PIDs as you're launching the daemons, it's possible that won't be the case.

For the moment, depending on what you're doing, you may be able to get away with taking the CD to another system and pfs-mounting it there, then NFS mounting it to the local system.

Oh, wait...maybe the patches listed above are the ones that let you mount this format of CD without explicitly using PFS at all? Just mount? Hmm.

HTH.

[Victor BERRIDGE]

Last chance: (may work, it did for me but once...)
stop all NFS activities:
cd /sbin/init.d
nfs.client stop
nfs.core stop
nfs.server stop

Now with luck you should be able to fuser -ku /cdrom

fuser -cku /dev/dsk/


umount /cdrom

and restart all nfs again...

Good luck
Victor

[bhavin asokan]

hi,

try the following

1.kill the pfs_mountd.rpc
2.start the pfs_mountd
#nohup /usr/sbin/pfs_mountd &
3.start the pfsd
#nohup /usr/sbin/pfsd &

now it should show four processes
/usr/sbin/pfs_mountd
pfs_mountd.rpc
/usr/sbin/pfsd
pfsd.rpc

then try to kill the umount process kill -9 20219 or umount the cdrom

regds,

[Yogeeraj_1]

hi,

you avoid using pfs_mount.

see Merijn's HP-UX software for ITRC members
at: http://www.cmve.net/~merijn/

(search for pfs_mount)

regards
yogeeraj