Nfsmnthelp Error - 1
Contents |
Facebook Twitter Google LinkedIn RSS Related posts Ways to Optimize IBM... Updated Likes 0 Comments 0 ITM Agent Insights: ... Updated
Nfsmnthelp: 1831-019
Likes 3 Comments 0 Simplified Remote Re... Updated Likes 0 Comments nfsmnthelp: 1831-019 system call error number -1 0 IBM Call Home Web - ... Updated Likes 0 Comments 0 How to create RHEL7 ... Updated mount 1831 008 giving up on vmount operation not permitted Likes 0 Comments 0 Similar Ideas Client Connectivity ... Ideation Blog: IBM PureData-... Apoorv Kapse 270003FSX5 Updated 0 Comments 0 Tags Solving the "System call error number -1"
Vmount: A File Or Directory In The Path Name Does Not Exist.
when you try to mount a NFS Torato 27000543R2 | | Visits (20295) Tweet Sometimes, when you try to mount a NFS on your server (even using the IP instead of hostname) you get the following error: I'm trying to mount a NFS on my server (hostname: server02 / IP: 10.0.10.16), that are exported by another server
Nfsmnthelp Aix
(hostname: server01 / IP: 10.0.10.15 )torator@server02:/home/torator # sudo mount 10.0.10.15:/tmp/TL12SP07 /TLnfsmnthelp: 1831-019 10.0.10.15: System call error number -1.mount: 1831-008 giving up on:10.0.10.15:/tmp/TL12SP07System call error number -1.torator@server02:/home/torator #How to solve this? It's very simple, you need to add on both servers an entry on /etc/hosts fileOn server01:10.0.10.16 server02On server02:10.0.10.15 server01After that, it's possible to mount the NFStorator@server02:/home/torator # sudo mount 10.0.10.15:/tmp/TL12SP07 /TLtorator@server02:/home/torator # df -g /TLFilesystem GB blocks Free %Used Iused %Iused Mounted on10.0.10.15:/tmp/TL12SP07 10.00 9.0 10% 2110 44% /TLtorator@server02:/home/torator # I expected that this can help you Tags:  call nfs aix number linux -1" mount system erro Login to access this feature Add a Comment More Actions v Notify Other People Notify Other People Comments (0) Add a Comment Edit More Actions v Quarantine this Entry notification Send Email Notification Type in a Name: + Notify: Message: Quarantine this entry Provide a reason for quarantining this blog entry (optional): deleteEntry duplicateEntry Mark as Duplicate Find the duplicate idea: Previous Entry Main Next Entry
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of nfsmnthelp: error -1 occurred. this site About Us Learn more about Stack Overflow the company Business
Nfsmnthelp: : Error -1 Occurred In Aix
Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question rpc: 1832-019 program not registered _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's https://www.ibm.com/developerworks/community/blogs/torator/entry/solving_the_system_call_error_number_1_when_you_try_to_mount_a_nfs4 how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top mknfsmnt fails with “System call error number -1” up vote 2 down vote favorite This system is part of a cluster and the other node mounts the nfs share successfully. This is currently the active node which means it has a secondary service http://unix.stackexchange.com/questions/191258/mknfsmnt-fails-with-system-call-error-number-1 ip address. I think this is related to the issue because I added the service ip to the nfs server /etc/hosts and it mounted fine. That is not a solution though. Why is a cluster ip confusing nfs? Edit: How does clustering complicate reverse lookup in relation to nfs? # mknfsmnt -f "/mksysb" -d "/export/mksysb" -h "10.0.28.119" '-n' '-N' '-a' -t 'rw' -w 'fg' '-Y' '-Z' '-X' '-H' '-j' '-q' '-g' nfsmnthelp: 1831-019 10.0.28.119: System call error number -1. mount: 1831-008 giving up on: 10.0.28.119:/export/mksysb System call error number -1. # showmount -e 10.0.28.119 export list for 10.0.28.119: /export/mksysb *.domain.com networking nfs aix cluster share|improve this question edited Mar 19 '15 at 19:48 asked Mar 19 '15 at 16:59 Shnifty 164 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote It seems like you answered your own question already with the /etc/hosts entry. I suggest looking at your working nodes and try to find any difference or discrepancy in the nfs server's resolution. share|improve this answer answered Mar 19 '15 at 18:42 Baazigar 45618 Name resolution works great though from both sides. Also, this isn'
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help https://www.experts-exchange.com/questions/25785199/nfsmnthelp-1831-019.html Receive Real-Time Help Create a Freelance Project Hire for a http://unix.derkeiler.com/Newsgroups/comp.unix.aix/2006-03/msg00019.html Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > nfsmnthelp 1831-019 Want to Advertise Here? Solved nfsmnthelp 1831-019 Posted on 2010-04-09 error - Server Software Unix OS 2 Verified Solutions 9 Comments 7,669 Views Last Modified: 2013-12-02 Hi Folks, What's wrong here? NFS mount fails as shown. Hosts can dig each other and dig -x each other's IPs. They are in each other's hosts files. Other tests shown... Many thanks, EDIT: Great, lost entire code section during post. : error -1 Redoing... host1:/ >mount host2:/usr/feeders /usr/feeders nfsmnthelp: 1831-019 host2: System call error number -1. mount: 1831-008 giving up on: host2:/usr/feeders System call error number -1. host1:/ >ping host2 PING host2.blah.blah.com: (host2IP): 56 data bytes 64 bytes from host2IP: icmp_seq=0 ttl=255 time=0 ms ----host2.blah.blah.com PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0/0/0 ms host1:/ >showmount -e host2IP export list for host2IP: /usr/feeders (everyone) host1:/ >lssrc -g nfs Subsystem Group PID Status biod nfs 4255778 active nfsd nfs 1069248 active rpc.mountd nfs 4276336 active rpc.statd nfs 794654 active rpc.lockd nfs 561214 active nfsrgyd nfs inoperative gssd nfs inoperative host1:/ >rpcinfo -p host2IP program vers proto port service 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 200
when trying to mount a directory. I've checked the daemons and they are started and I've checked the exportfs on the source server and it's open. Here's the error... rs999e# mount rs240ii:/miscware/patrol /mnt nfsmnthelp: rs240ii: Error -1 occurred. mount: giving up on: rs240ii:/miscware/patrol Error -1 occurred. daemons running.... rs999e# lssrc -g nfs Subsystem Group PID Status biod nfs 15246 active rpc.statd nfs 7358 active rpc.lockd nfs 17548 active nfsd nfs 29508 active rpc.mountd nfs 33224 active exportfs.... rs240ii:exportfs /miscware/patrol -sec=sys,rw what's going on or what am I not looking at. IIRC, with sec=sys, the server must be able to resolve the IP of the client back to a hostname. -- Doing AIX support was the most monty-pythonesque activity available at the time. Eagerly awaiting my thin chocolat mint. . Follow-Ups: Re: Can't mount NFS directory From: KB Prev by Date: Re: SCSI Media Changer device drive AIX 5.3 Next by Date: Re: how to read core file Previous by thread: Re: Reference main globals and functions in .so Next by thread: Re: Can't mount NFS directory Index(es): Date Thread Flag as inappropriate (AWS) Security UNIX Linux Coding Usenet Mailing-ListsNewsgroupsAboutPrivacyImprint unix.derkeiler.com >Newsgroups >comp.unix.aix >2006-03