Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

nfs help on AIX 5.3

Status
Not open for further replies.

jprabaker

Technical User
May 31, 2001
185
GB
Guys,

I'm getting the following when trying to mount a remote NFS share on an AIX client: (both server and client are at 5300-05)

nfsmnthelp: 1831-019 testlpar: System call error number -1.

mount: 1831-008 giving up on:
testlpar:/usr/sys/inst.images
System call error number -1.

I've set the share up in the default manner, just specifing the pathname to export. My clients can see the share via a showmount -e, but both error when trying to mount.

Cheers,
John
 
restart the nfs deamon on both nodes and reshare the server mount again. then try it from the client and see how it goes

That's how i usually debug nfs problems!

Good luck
Khalid
 
are you sure about oslevel on nfs server? I've seen similar things when nfs server on 5300-02 if I remember right.


HTH,

p5wizard
 
oslevel is 5300-05-04 on both client and server. I can mount the filesystem on the nfs server, but thats no use to me!
 
you will have to re-export the filesystem from the server and then try to mount it on the client (after stopsrc and startsrc for nfs)

stopsrc -g nfs
startsrc -g nfs

on both machines

Regards,
Khalid
 
khalidaaa,

I don't see the validity in doing that, but done so anyway to no avail.
 
I'm thinking it's more to do with nfs version 4, but I've tried exporting the filesystems as version2, still with no luck. My only other thoughts are towards hostname resolution, but I can't see why! Has no-one else seen this error? My setup is pretty much standard, very little customisation yet, all machines are new builds on new kit, all on 5300-05-04. I need to get NIM up and running so NFS is critical....
 
google for:
site:ibm.com 1831-008 giving up on
for some ideas
 
Thanks Duke. DNS is the culprit. If I do an nslookup on the hostname it returns the IP, if I do an nslookup on the ip address the dns server can't find it.

Our DNS is not working properly & needs a re-build (not my job :) In the meantime I've got it working through adding the hostnames into /etc/hosts on both client & server.

Thanks for all the responses!
 
don't forget to remove them from the hosts file when DNS is fixed, or they will come back and bite you one day!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top