System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

NFS MOUNT GIVES UNKNOWN ERROR

so_2
Regular Advisor

NFS MOUNT GIVES UNKNOWN ERROR

We are trying to mount a filesystem exported on ann AIX machine to a HPux11.11 machine.
while trying to mount we are getting "unknown error" and terminates.
we had checked all the services and daemons both on server and client.
We are able to mount the directories exporetd from HPUX 11 server to the same AIX server.
We tried mounting directories from other servers either but gives same error.
tried changing the mount directories, but still fails.
pls find the attachment.
and help me as i am back to it for 3 days.
S.O


19 REPLIES
Peter Godron
Honored Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Hi,
as a starting point, can the HPUX machine see the AIX box? Is edcdbs12 defined in /etc/hosts ?
so_2
Regular Advisor

Re: NFS MOUNT GIVES UNKNOWN ERROR

yes peter,

actually iam trying to mount from edcdbs13.edcdbs12 have been used to test on another to confirm that the problem was not with server.


pls find the details below .


# rpcinfo -p edcdbs13
program vers proto port service
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
200006 1 udp 2049
200006 1 tcp 2049
100005 1 tcp 32769 mountd
100005 2 tcp 32769 mountd
100005 3 tcp 32769 mountd
100005 1 udp 32880 mountd
100005 2 udp 32880 mountd
100005 3 udp 32880 mountd
100021 1 udp 32882 nlockmgr
100021 2 udp 32882 nlockmgr
100021 3 udp 32882 nlockmgr
100021 4 udp 32882 nlockmgr
100021 1 tcp 32770 nlockmgr
100021 2 tcp 32770 nlockmgr
100021 3 tcp 32770 nlockmgr
100021 4 tcp 32770 nlockmgr
100024 1 tcp 32771 status
100024 1 udp 32881 status
100133 1 tcp 32771
100133 1 udp 32881
200001 1 tcp 32771
200001 1 udp 32881
200001 2 tcp 32771
200001 2 udp 32881
200001 2 udp 32881
# nslookup edcdbs13
Using /etc/hosts on: edcdbs11

looking up FILES
Name: edcdbs13
Address: 10.31.1.151

#

John Waller
Esteemed Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

This might seem like a silly suggestion, but could you run a "which mount" command to confirm that you are running /usr/sbin/mount. I've never seen the "Unknown error" message so I am wondering whether somebody have wrote a script called mount which you are calling by mistake.
so_2
Regular Advisor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Any thing you feel in mind can be write here.I am sure that it could be a simple problem, but I am in a loop. To come out of the loop you may suggest any silly solution.
tried " which" and result is /usr/sbin/mount

when i am trying to mount using" -o vers=2 "option it gives an error message

" nfs mount :get_fh unknow error"
John Waller
Esteemed Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Have you tried adding the mount via SAM.

Networking & Communications -> Networked File Systems -> Mounted Remote File Systems.

This might give you a bit more information about the failure.

so_2
Regular Advisor

Re: NFS MOUNT GIVES UNKNOWN ERROR

again the same message is given by SAM.

I am able to mount the AIX dir to other HP machines.

I am able to mount other HP dir to this HP.

Only thing is i am unable to mount IBM to this HP.
Lolupee
Regular Advisor

Re: NFS MOUNT GIVES UNKNOWN ERROR

can you just remove everyone or instead of puting everyone in bracket comment it. i.e leave /tmp alone on the line in the /etc/export file

then run exportfs -a -v again.

after that go back to the client and try to mount.

/tmp #everyone
Lolupee
Regular Advisor

Re: NFS MOUNT GIVES UNKNOWN ERROR

can you just remove everyone or instead of puting everyone in bracket comment it. i.e leave /tmp alone on the line in the /etc/export file of the server

/tmp #everyone

then run exportfs -a -v again from server

after that go back to the client and try to mount.

John Waller
Esteemed Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Could it be possible to list the contents of the /etc/exports file from the AIX server and also the output from a oslevel -r command.

Also are the working HP servers also hpux 11.11 and are they at the same location as your failing server. Could you have a firewall between the AIX and HP servers which is causing the problem.

I have access to AIX 4.3, 5.1, 5.2 and 5.3 but cannot replicate your problem so I know it does work.
Victor BERRIDGE
Honored Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

My 2 cents...
If you were to have difficulties such as mismatch from the boxes you would have denial messages such as connection refused by...

Since you can mount on other boxes..., have you thought of /sbin/init.d/nfs.client stop/start ?
Just to be sure...


All the best
Victor
so_2
Regular Advisor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Thanks for all your suggestions.
I had already restaretd the NFS client on my HP machine. There are no firewall. All HP and AIX servers are on the same network.
I am not getting any NFS error messages.
I dont thinks "Unkonwn error " is a NFS error message.

if any one have some more answer on it , let it be too simple pls put it here to follow.
the issue is still open.

thanks
s.o
so_2
Regular Advisor

Re: NFS MOUNT GIVES UNKNOWN ERROR

On further investigation, it has observed that we are able to mount the AIX directory only on HP running 10.xx. I have 2 HP running 11.11 on both i am unable to mount.

pls help if you can get something from above observation.

s.o
Patrick Wallek
Honored Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

If I remember correctly, NFS on HP-UX 10.20 ran over UDP, and I believe NFS on 11.11 runs over TCP by default.

Try this using '-o vers=2 -o proto=udp' in your NFS mount options and see if it helps.
so_2
Regular Advisor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Thanks patrik

we tried this option already. same unknown error is giving. is there any patch to be installed either on AIX or on HP to work?

thanks
s.o
Victor BERRIDGE
Honored Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Lets start from 0 again then:
1) What aix version is this box
2)You can mount this nfs-FS on other HP box but not on this one OK?
Can you mount another nfs-FS from another aix box on this server?
3)Can this box mount nfs-FS from other hpux?
Can this HP box export to your aix and can your aix mount the FS?

All the best
Victor
Sameer_Nirmal
Honored Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Hi,

Looking at the "rpcinfo" output, it seems that IBM NFS server does support ver 1 of mountd(rpc.mountd). It maybe a case and since it allows mount on HP-UX 10.x, the mountd ver 1 is fixed at AIX side, check "nfsconf" or similar and look for a defination for mountd.
If it is not fixed , there could a patch or something at AIX nfs side which would switch the mountd versions depending on the mount request from a client.
Dave Olker
HPE Pro

Re: NFS MOUNT GIVES UNKNOWN ERROR

Hi S.O.

The unknown error could be caused by a number of issues; some temporary and could be cleared by a reboot, others not. If you are able, I'd try rebooting the 11.11 system to see if the problem goes away after the reboot.

If not, the next piece of data to collect would be a network packet trace of the failing mount command. Please collect the trace on the 11.11 system using either nettl or ethereal and post the raw trace file here so that we can examine the trace to see if it shows why the mount is failing.

Regards,

Dave
Deoncia Grayson_1
Honored Contributor

Re: NFS MOUNT GIVES UNKNOWN ERROR

What version of AIX are you running? This may be compatibility issue between the two OS.
If no one ever took risks, Michelangelo would have painted the Sistine floor. -Neil Simon
Jorge_A_Rivera
Occasional Visitor

Re: NFS MOUNT GIVES UNKNOWN ERROR

Hello,
We passed something like that with the same error.

 

ping from AIX machine to the HPux11.11name and the ip address.


Please check if the HPux11.11 machine IP Address is correct in the /etc/host file on AIX machine. Maybe you are not using DNS and the authentication is by /etc/hosts. May be the name is ok but not the IP Address.
In our case was an error in a only one numer in the IP Address.