Tru64 / HP-UX NFS mount problem

RockmanExe · 05-02-2006, 12:17 PM

Hello:

Recently, we did a NFS mount from a Tru64 Server to another HP-UX server ,by typing:

"mount hostname:/cdrom": being /cdrom the shared filesystem. Everything went fine.
Then somebody forgot to umount the NFS mount in the Tru64 server and closed the remote session, later on, the HPUX server was shutdown and now everytime the HPUX is down, the Tru64 is always asking for the NFS as still mounted, however this mounting is nowhere to be found, not declared in /etc/fstab nor /etc/mountdtabs and so on.

How can in definitely umount this fileystem? the real problem is the once the HPUX server is asking for the NFS lost filesystem, it cant even do a simple "ls"

Regards

satinet · 05-03-2006, 05:32 AM

what's the output of the "mount" command? (just mount on it's own).

have you tried stopping the NFS daemon?

/sbin/init.d/nfs.client stop

and/or

/sbin/init.d/nfs.server stop

RockmanExe · 05-03-2006, 09:25 AM

thanks for your reply,
mount command shows nothing related to the NFS mount, restarting NFS daemon is maybe a little risky, since it's a production server and there are other working NFS shares spread over the network.
on the NFS server, the command "showmount -a" displays that indeed the remote client is still "stuck" under /cdrom.

Maybe i should try remounting the same filesystem and umount it correctly this time?

Regards

satinet · 05-03-2006, 09:40 AM

have you tried terminating the process on the client server? i.e grepping for the nfs process........

RockmanExe · 05-03-2006, 11:08 AM

Not yet, i'll try. On the other hand, we found the very roots of the problem: the NFS mount point was removed from the client (i don't know why) and now everytime we try to recreate it (it was called /cdrom as well) there's an error message:

cdrom: Stale NFS file handle

Again, the client is a heavy production server and can't be rebooted or something drastic, i'll follow your suggestion about grepping the nfs proccesses

Thank you

satinet · 05-03-2006, 11:12 AM

i strongly recommend you visit:
www.itrc.hp.com/

not that there's anything wrong with LQ. but this is specific to hp-ux... and there are some amazing experts there......

http://forums1.itrc.hp.com/service/f...hreadId=996618

looks like killing processes or rebooting the tru64 are your main chances....

i would do something like this:

fuser -cuk /stale

stale being the mount point......