cannot access nfs3-specific umount command

[Mike Rightmire]

Hey Gang,

I updated my HP-UX 10.20 server to NFS3. I have Ignite (which attempts to mount /var/opt/ignite/client.mnt to igniteserver:/var/opt/ignite/clients) and it is failing and offering the error "cannot access nfs3-specific umount command". The directory IS already mounted and Ignite needs to UN-mount it and mount it again.

When I tried to umount the directory on the box itself (not the ignite server, but the machine I am trying to back up) I get the same error message when I type ...

umount /var/opt/ignite/client.mnt

None of the umount commands on the machine (nor ones copied from a different machine with NFS3) will function.

HELP!

[Vincent Stedema]

Mike,

What does nfsstat say about the NFS version for this specific mount?

nfsstat -m and look at the "vers" entry.

[Brian Hackley]

Mike,

Try copying over /sbin/fs/nfs/umount
from a system where NFS PV3 is already installed and working, and see if that helps
to resolve the issue. The (u)mount command redirects to Filesystem specfic (u)mount
commands.

Hope this helps,

-> Brian Hackley

[Mike Rightmire]

Well...no luck. When I use the nfsstat -m on the system, almost all the mounted directories are ver 3. I CAN mount a directory (and it mounts it using version 3 just fine) but I cannot unmount the directory.

I tried copying over the umount command as recommended, but it had no effect. When I installed nfs v.3, I did have to modify the config file to tell it to use version 3, however it is the same modifications I made on the other system after installing version 3 which is working fine.

[Patrick Wallek]

Mike,

Check this document in the TKB. I think this will help you.

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=2a1bd9b213bcdda0d6/screen=ckiSearchResults

[Mike Rightmire]

Patrick,

When I click the link, I just go to the search screen and get a message that I must enter search criteria. Could you possible go to the document itself and send me the link?

Thanks in advance,
Mike

[Patrick Wallek · Accepted solution]

Sorry Mike. I thought that was the link to the document.

Try this one: http://us-support2.external.hp.com/cki/bin/doc.pl/sid=ead1869513b0a3cd82/screen=ckiDisplayDocument?docId=200000024646055

Just in case the link doesn't work, here is the Solution from that document:

Solution

Sounds the kernel portion of PV3 is installed, but the user-space is
not. Since you have not installed the B6378/9 bundles, you might have the PATCH_NOSAVE file on the system, which would cause the patch installations to be altered.

Do the following steps to correct this problem:

1. Make sure the PATCH_NOSAVE file is not being used
2. Make sure the following files do not exist:
/sbin/fs/autofs/mount
/sbin/fs/cachefs/mount

3. Re-apply PHNE_14072 and PHNE_13731 to force the PV2 kernel and user-space bits to be used.


Note that the two above mentioned patches have probably been superseded.

[Mike Rightmire]

Thanks Patrick!

That got nme too the document. One question I have about it...will thi leave me running version 2 or ver 3. I do have to have ver 3 running, in order for Ignite to continue to work.

I got to version 3 by installing PHNE_22117. The document mentiones different patches. Should I remove the files mentioned in the document, then reinstall 22117?

Any advice is GREATLY appreciated!
Mike

[Patrick Wallek]

Mike,

The two patches mentioned in that document have been superseded, so has PHNE_22117, which you installed.

The newest patches are PHNE_22877 and PHNE_22288. I started going through the patch database checking dependecies, and these patches have a LOT of dependencies. PHNE_22877 will have a dependencie of another patch, which then depends on another, etc. I was going to try to give you a complete list of patches, but I got tired of trying to figure out all the dependencies. That in itself may be part of your problem. If you just installed PHNE_22117 and not any of the dependent patches, then that can really cause problems.

Good luck!

[Mike Rightmire]

Hey Folks,

The final answer was a simple one. The patches were good. I needed to do the following to get it corrected...

Made sure the PATCH_NOSAVE file was not being used

Renamed the following files ...
/sbin/fs/autofs/mount
/sbin/fs/cachefs/mount
... so the system could not see them.

Created a link in the sbin.fs directory called nfs3, pointing to nfs using the following command ...

ln -s /sbin/fs/nfs /sbin/fs/nfs3

Everything seems to be mounting and unmounting now!

Thanks for all the help!
Mike