Fedora Linux Support Community & Resources Center
  #1  
Old 27th May 2008, 03:07 AM
jmbnyc Offline
Registered User
 
Join Date: Jun 2007
Posts: 36
nfs internal error

I am unable to mount any file systems after upgrading to F9. All of these mounts worked previously (FC2-FC8).

mount -v 192.168.0.107:/SHARE1 /share1
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Mon May 26 22:06:44 2008
mount.nfs: text-based options: 'addr=192.168.0.107'
mount.nfs: internal error

Any help would be appreciated - this drive has my svn repo and I need to get it mounted.
/JMB
Reply With Quote
  #2  
Old 27th May 2008, 05:11 AM
sri_ram1982 Offline
Registered User
 
Join Date: Apr 2005
Location: India
Age: 32
Posts: 90
you need to specify the file system type. mount -t nfs.Is the portmap service also running there.
Reply With Quote
  #3  
Old 27th May 2008, 05:31 AM
jmbnyc Offline
Registered User
 
Join Date: Jun 2007
Posts: 36
everything I try fails:

mount -v -t nfs 192.168.0.107:/SHARE1 /share1

I even tried via fstab:
192.168.0.107:/SHARE1 /share1 nfs hard,intr,bg,nolock,rw 0 0

mount -a -t nfs

all give the same error:
mount.nfs: timeout set for Tue May 27 00:31:53 2008
mount.nfs: text-based options: 'addr=192.168.0.107'
mount.nfs: internal error
Reply With Quote
  #4  
Old 27th May 2008, 06:00 AM
brunson Offline
Registered User
 
Join Date: Jun 2005
Location: Westminster, Colorado
Posts: 2,306
See if there are any more informative messages /var/log/messages. Otherwise look in the man page to see if there's any way to coerce the mount command to give up more info.
__________________
Registered Linux User #4837
411th in line to get sued by Micro$oft
Quote:
Basically, to learn Unix you learn to understand and apply a small set of key ideas and achieve expertise by expanding both the set of ideas and your ability to apply them - Paul Murphy
Reply With Quote
  #5  
Old 2nd June 2008, 01:32 AM
jcasey Offline
Registered User
 
Join Date: Mar 2007
Posts: 3
I am getting the same error mounting NFS directories "mount.nfs: internal error" on FC9. This mount point has been working fine every since FC4 through FC8. So I can only assume the mount.nfs program/protocol changed or a bug was introduced in FC9.

relevant entry in /etc/fstab
192.168.56.100rive1 /mnt/snap nfs defaults 0 0

rpm versions:
nfs-utils-1.1.2-2.fc9.i386
nfs-utils-lib-1.1.1-3.fc9.i386

This system was upgraded from FC8 so in order to eliminate any upgrade inconsistencies, I did a fresh install of fc9 on a new disk and got the same mount.nfs: internal error.

Can anyone help? I'll also do a bugzilla report if it does not already exist.

Also, can anyone confirm that the FC9 gdm can no longer support remote xdmcp requests? This is one other thing I've noticed in FC9 that was working in FC8 and before. I tried editing the custom.conf according to the fedora.live page referenced in the release notes, but got no joy. \\

Thanks in advance.
Reply With Quote
  #6  
Old 2nd June 2008, 10:28 AM
mipsnice Offline
Registered User
 
Join Date: Jun 2008
Location: Nice - France
Posts: 3
Hi,

i have the same problem.
I have 150 Fedora WorkStations and 10 Linux servers under Debian4.0, Solaris, FC7 and tru64/OSF1 AlphaServer (HP).

With FC6-FC8, all the NFS mount work perfectly but with FC9, i can't mount the filesytems exported by the tru64/OSF1 AlphaServer.

I have only this message :
# mount.nfs alphaserver:/home/toto /mnt/tmp -v
mount.nfs: timeout set for Mon Jun 2 11:17:13 2008
mount.nfs: text-based options: 'addr=134.59.2.99'
mount.nfs: internal error

I have tested with differents options :
-o timeo=3600 -o retrans=10 -o mountvers=3 -o nfsvers=2 ...

but it's always the same error.

rpcinfo seem ok :
# rpcinfo -s alphaserver
program version(s) netid(s) service owner
100000 2 udp,tcp portmapper unknown
100004 1,2 tcp,udp ypserv unknown
100007 1,2 udp,tcp ypbind unknown
100005 3,1 tcp,udp mountd unknown
100003 3,2 tcp,udp nfs unknown
100024 1 tcp,udp status unknown
100021 4,3,2,1 udp,tcp nlockmgr unknown
100020 3 udp,tcp llockmgr unknown
100011 1 udp rquotad unknown
100068 4,3,2 udp - unknown
100083 1 tcp - unknown

I repeat : until FC8, the mounting was OK. I made only a upgrade FC8 -> FC9.

nfs-utils-1.1.2-2.fc9.i386
nfs-utils-lib-1.1.1-3.fc9.i386

What can we do ?
Thanks you very much for your help and answers.
Reply With Quote
  #7  
Old 2nd June 2008, 01:29 PM
mipsnice Offline
Registered User
 
Join Date: Jun 2008
Location: Nice - France
Posts: 3
And, this is the debug info !

Jun 2 14:11:33 amazone kernel: NFS: nfs mount opts='addr=192.168.2.99'
Jun 2 14:11:33 amazone kernel: NFS: parsing nfs mount option 'addr=192.168.2.99'
Jun 2 14:11:33 amazone kernel: NFS: sending MNT request for alphaserver:/home/toto
Jun 2 14:11:33 amazone kernel: RPC: set up transport to address addr=192.168.2.99 port=0 proto=udp
Jun 2 14:11:33 amazone kernel: RPC: created transport e5caa800 with 16 slots
Jun 2 14:11:33 amazone kernel: RPC: creating mount client for alphaserver (xprt e5caa800)
Jun 2 14:11:33 amazone kernel: RPC: creating UNIX authenticator for client e5c4e000
Jun 2 14:11:33 amazone kernel: RPC: 0 holding NULL cred f8f21b8c
Jun 2 14:11:33 amazone kernel: RPC: new task initialized, procpid 11411
Jun 2 14:11:33 amazone kernel: RPC: allocated task f7b24400
Jun 2 14:11:33 amazone kernel: RPC: 1115 __rpc_execute flags=0x280
Jun 2 14:11:33 amazone kernel: RPC: 1115 call_start mount3 proc 0 (sync)
Jun 2 14:11:33 amazone kernel: RPC: 1115 call_reserve (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1115 reserved req e5c45000 xid 219e5c95
Jun 2 14:11:33 amazone kernel: RPC: 1115 call_reserveresult (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1115 call_allocate (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1115 allocated buffer of size 92 at f015b000
Jun 2 14:11:33 amazone kernel: RPC: 1115 call_bind (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1115 rpcb_getport_async(alphaserver, 100005, 3, 17)
Jun 2 14:11:33 amazone kernel: RPC: 1115 sleep_on(queue "xprt_binding" time 26146008)
Jun 2 14:11:33 amazone kernel: RPC: 1115 added to queue e5caa8a4 "xprt_binding"
Jun 2 14:11:33 amazone kernel: RPC: 1115 setting alarm for 60000 ms
Jun 2 14:11:33 amazone kernel: RPC: 1115 rpcb_getport_async: trying rpcbind version 4
Jun 2 14:11:33 amazone kernel: RPC: set up transport to address addr=192.168.2.99 port=111 proto=udp
Jun 2 14:11:33 amazone kernel: RPC: created transport e5caa400 with 16 slots
Jun 2 14:11:33 amazone kernel: RPC: creating rpcbind client for alphaserver (xprt e5caa400)
Jun 2 14:11:33 amazone kernel: RPC: creating UNIX authenticator for client e5c4e200
Jun 2 14:11:33 amazone kernel: RPC: 0 looking up UNIX cred
Jun 2 14:11:33 amazone kernel: RPC: new task initialized, procpid 11411
Jun 2 14:11:33 amazone kernel: RPC: allocated task f23e3100
Jun 2 14:11:33 amazone kernel: RPC: 1116 __rpc_execute flags=0x281
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_start rpcbind4 proc 9 (async)
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_reserve (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1116 reserved req e5c44000 xid e302dd83
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_reserveresult (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_allocate (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1116 allocated buffer of size 540 at f015b800
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_bind (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_connect xprt e5caa400 is not connected
Jun 2 14:11:33 amazone kernel: RPC: 1116 xprt_connect xprt e5caa400 is not connected
Jun 2 14:11:33 amazone kernel: RPC: 1116 xprt_cwnd_limited cong = 0 cwnd = 256
Jun 2 14:11:33 amazone kernel: RPC: 1116 sleep_on(queue "xprt_pending" time 26146009)
Jun 2 14:11:33 amazone kernel: RPC: 1116 added to queue e5caa528 "xprt_pending"
Jun 2 14:11:33 amazone kernel: RPC: 1116 setting alarm for 5000 ms
Jun 2 14:11:33 amazone kernel: RPC: xs_connect scheduled xprt e5caa400
Jun 2 14:11:33 amazone kernel: RPC: rpc_release_client(e5c4e200)
Jun 2 14:11:33 amazone kernel: RPC: 1115 sync task going to sleep
Jun 2 14:11:33 amazone kernel: RPC: disconnected transport e5caa400
Jun 2 14:11:33 amazone kernel: RPC: 1116 __rpc_wake_up_task (now 26146009)
Jun 2 14:11:33 amazone kernel: RPC: 1116 disabling timer
Jun 2 14:11:33 amazone kernel: RPC: 1116 removed from queue e5caa528 "xprt_pending"
Jun 2 14:11:33 amazone kernel: RPC: __rpc_wake_up_task done
Jun 2 14:11:33 amazone kernel: RPC: xs_bind4 0.0.0.0:0: ok (0)
Jun 2 14:11:33 amazone kernel: RPC: worker connecting xprt e5caa400 to address: addr=192.168.2.99 port=111 proto=udp
Jun 2 14:11:33 amazone kernel: RPC: 1116 __rpc_execute flags=0x281
Jun 2 14:11:33 amazone kernel: RPC: 1116 deleting timer
Jun 2 14:11:33 amazone kernel: RPC: 1116 xprt_connect_status: connection broken
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_connect_status (status -107)
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_timeout (minor)
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_bind (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_connect xprt e5caa400 is connected
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_transmit (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1116 xprt_prepare_transmit
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_encode (status 0)
Jun 2 14:11:33 amazone kernel: RPC: 1116 marshaling UNIX cred f6f6f480
Jun 2 14:11:33 amazone kernel: RPC: 1116 using AUTH_UNIX cred f6f6f480 to wrap rpc data
Jun 2 14:11:33 amazone kernel: RPC: rpcb_encode_getaddr(100005, 3, 192.168.2.99.0.111)
Jun 2 14:11:33 amazone kernel: RPC: 1116 xprt_transmit(152)
Jun 2 14:11:33 amazone kernel: RPC: xs_udp_send_request(152) = 152
Jun 2 14:11:33 amazone kernel: RPC: 1116 xmit complete
Jun 2 14:11:33 amazone kernel: RPC: 1116 sleep_on(queue "xprt_pending" time 26146009)
Jun 2 14:11:33 amazone kernel: RPC: 1116 added to queue e5caa528 "xprt_pending"
Jun 2 14:11:33 amazone kernel: RPC: 1116 setting alarm for 10000 ms
Jun 2 14:11:33 amazone kernel: RPC: xs_udp_data_ready...
Jun 2 14:11:33 amazone kernel: RPC: cong 256, cwnd was 256, now 512
Jun 2 14:11:33 amazone kernel: RPC: wake_up_next(e5caa4fc "xprt_resend")
Jun 2 14:11:33 amazone kernel: RPC: wake_up_next(e5caa4d0 "xprt_sending")
Jun 2 14:11:33 amazone kernel: RPC: 1116 xid e302dd83 complete (24 bytes received)
Jun 2 14:11:33 amazone kernel: RPC: 1116 __rpc_wake_up_task (now 26146010)
Jun 2 14:11:33 amazone kernel: RPC: 1116 disabling timer
Jun 2 14:11:33 amazone kernel: RPC: 1116 removed from queue e5caa528 "xprt_pending"
Jun 2 14:11:33 amazone kernel: RPC: __rpc_wake_up_task done
Jun 2 14:11:33 amazone kernel: RPC: 1116 __rpc_execute flags=0x281
Jun 2 14:11:33 amazone kernel: RPC: 1116 deleting timer
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_status (status 24)
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_decode (status 24)
Jun 2 14:11:33 amazone kernel: RPC: 1116 validating UNIX cred f6f6f480
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_verify: program 100000 is unsupported by server alphaserver
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_verify: call failed with error -96
Jun 2 14:11:33 amazone kernel: RPC: setting port for xprt e5caa800 to 0
Jun 2 14:11:33 amazone kernel: RPC: 1116 rpcb_getport_done(status -96, port 0)
Jun 2 14:11:33 amazone kernel: RPC: 1115 __rpc_wake_up_task (now 26146010)
Jun 2 14:11:33 amazone kernel: RPC: 1115 disabling timer
Jun 2 14:11:33 amazone kernel: RPC: 1115 removed from queue e5caa8a4 "xprt_binding"
Jun 2 14:11:33 amazone kernel: RPC: __rpc_wake_up_task done
Jun 2 14:11:33 amazone kernel: RPC: 1116 return 0, status -96
Jun 2 14:11:33 amazone kernel: RPC: 1116 release task
Jun 2 14:11:33 amazone kernel: RPC: freeing buffer of size 540 at f015b800
Jun 2 14:11:33 amazone kernel: RPC: 1116 release request e5c44000
Jun 2 14:11:33 amazone kernel: RPC: wake_up_next(e5caa554 "xprt_backlog")
Jun 2 14:11:33 amazone kernel: RPC: 1116 releasing UNIX cred f6f6f480
Jun 2 14:11:33 amazone kernel: RPC: rpc_release_client(e5c4e200)
Jun 2 14:11:33 amazone kernel: RPC: destroying rpcbind client for alphaserver
Jun 2 14:11:33 amazone kernel: RPC: destroying transport e5caa400
Jun 2 14:11:33 amazone kernel: RPC: xs_destroy xprt e5caa400
Jun 2 14:11:33 amazone kernel: RPC: xs_close xprt e5caa400
Jun 2 14:11:33 amazone kernel: RPC: disconnected transport e5caa400
Jun 2 14:11:33 amazone kernel: RPC: 1115 sync task resuming
Jun 2 14:11:33 amazone kernel: RPC: 1115 deleting timer
Jun 2 14:11:33 amazone kernel: RPC: 1115 remote rpcbind service unavailable
Jun 2 14:11:33 amazone kernel: RPC: 1115 return 0, status -5
Jun 2 14:11:33 amazone kernel: RPC: 1115 release task
Jun 2 14:11:33 amazone kernel: RPC: freeing buffer of size 92 at f015b000
Jun 2 14:11:33 amazone kernel: RPC: 1115 release request e5c45000
Jun 2 14:11:33 amazone kernel: RPC: wake_up_next(e5caa954 "xprt_backlog")
Jun 2 14:11:33 amazone kernel: RPC: 1115 releasing NULL cred f8f21b8c
Jun 2 14:11:33 amazone kernel: RPC: rpc_release_client(e5c4e000)
Jun 2 14:11:33 amazone kernel: RPC: shutting down mount client for alphaserver
Jun 2 14:11:33 amazone kernel: RPC: rpc_release_client(e5c4e000)
Jun 2 14:11:33 amazone kernel: RPC: destroying mount client for alphaserver
Jun 2 14:11:33 amazone kernel: RPC: destroying transport e5caa800
Jun 2 14:11:33 amazone kernel: RPC: xs_destroy xprt e5caa800
Jun 2 14:11:33 amazone kernel: RPC: 1116 freeing task
Jun 2 14:11:33 amazone kernel: RPC: disconnected transport e5caa800
Jun 2 14:11:33 amazone kernel: NFS: failed to create RPC client, status=-5
Jun 2 14:11:33 amazone kernel: NFS: unable to mount server alphaserver, error -5RPC: 1115 freeing task
Reply With Quote
  #8  
Old 2nd June 2008, 03:46 PM
mipsnice Offline
Registered User
 
Join Date: Jun 2008
Location: Nice - France
Posts: 3
Quote:
Originally Posted by mipsnice
Jun 2 14:11:33 amazone kernel: RPC: 1116 call_verify: program 100000 is unsupported by server alphaserver
The calls from FC9 seems no more compatible with portmap (program 100000) on the AlphaServer.

It's seems a bug of the FC9.
Reply With Quote
  #9  
Old 9th June 2008, 11:42 AM
marktiller Offline
Registered User
 
Join Date: Feb 2005
Posts: 5
Does anyone know if there is a fix for this yet?
Reply With Quote
  #10  
Old 10th June 2008, 09:23 PM
jmbnyc Offline
Registered User
 
Join Date: Jun 2007
Posts: 36
Quote:
Originally Posted by marktiller
Does anyone know if there is a fix for this yet?
I have not yet found a fix - lots of people seem to have the problem but no solution. I posted a bug on bugzilla but so far the ball has not moved.
Reply With Quote
  #11  
Old 12th June 2008, 08:14 PM
mooninite Offline
Registered User
 
Join Date: Nov 2004
Posts: 69
Guys, please follow up on the Red Hat bugzilla.

https://bugzilla.redhat.com/show_bug.cgi?id=448898
__________________
Lulz
Reply With Quote
  #12  
Old 13th June 2008, 03:00 AM
jmbnyc Offline
Registered User
 
Join Date: Jun 2007
Posts: 36
Quote:
Originally Posted by mooninite
Guys, please follow up on the Red Hat bugzilla.

https://bugzilla.redhat.com/show_bug.cgi?id=448898
A bug was opened (by me) on June 3rd. Bug #448898.
Reply With Quote
  #13  
Old 25th June 2008, 01:14 AM
jcasey Offline
Registered User
 
Join Date: Mar 2007
Posts: 3
mount.nfs: internal error fedora 9 - more info

More info on mount.nfs: internal error problem
Here's the kernel rpc debug output for

mount.nfs snap:/Drive1 /mnt/snap
mount.nfs: internal error

dmesg returns>
RPC: creating mount client for snap (xprt ddcf0000)
RPC: 23 call_start mount3 proc 0 (sync)
RPC: 23 call_reserve (status 0)
RPC: 23 call_reserveresult (status 0)
RPC: 23 call_allocate (status 0)
RPC: 23 call_bind (status 0)
RPC: creating rpcbind client for snap (xprt ccca8c00)
RPC: 24 call_start rpcbind4 proc 9 (async)
RPC: 24 call_reserve (status 0)
RPC: 24 call_reserveresult (status 0)
RPC: 24 call_allocate (status 0)
RPC: 24 call_bind (status 0)
RPC: 24 call_connect xprt ccca8c00 is not connected
RPC: rpc_release_client(f318b200)
RPC: 24 call_connect_status (status -107)
RPC: 24 call_timeout (minor)
RPC: 24 call_bind (status 0)
RPC: 24 call_connect xprt ccca8c00 is connected
RPC: 24 call_transmit (status 0)
RPC: 24 call_encode (status 0)
RPC: 24 call_status (status 24)
RPC: 24 call_decode (status 24)
RPC: 24 call_verify: proc f8c4efec unsupported by program 100000, version 4 on server snap
RPC: 24 call_verify: call failed with error -95
RPC: rpc_release_client(f318b200)
RPC: destroying rpcbind client for snap
RPC: 23 unrecognized rpcbind error (95)
RPC: rpc_release_client(f304ba00)
RPC: shutting down mount client for snap
RPC: rpc_release_client(f304ba00)
RPC: destroying mount client for snap
Reply With Quote
  #14  
Old 1st July 2008, 04:29 PM
spacelobsters Offline
Registered User
 
Join Date: Jun 2006
Age: 71
Posts: 149
same problem for me, firewall is disabled, nfs service is running, rpcinfo -p returns results.
Both my systems run fedora 9, clean installs.
__________________
registered linux user 420229
fluxbox & gnome user
Reply With Quote
  #15  
Old 2nd July 2008, 01:41 PM
spacelobsters Offline
Registered User
 
Join Date: Jun 2006
Age: 71
Posts: 149
The issue seems to be to do with not allowing the correct ports, I disabled both firewalls using system-config-firewall. That did nothing.
So I enabled both firewalls again and stopped the iptables service on the nfs server instead and that did it, so now I can mount nfs shares. Though not a very elegant solution. I'll check out which ports I am missing to see what the real problem is.
__________________
registered linux user 420229
fluxbox & gnome user
Reply With Quote
Reply

Tags
error, internal, nfs

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
bug in GCC 4.4 with OpenMP (internal error) mario.storti Using Fedora 0 3rd October 2009 11:15 PM
FC9 nfs internal error again pwalden Using Fedora 4 2nd February 2009 08:08 PM
PackageKit Error - Internal System Error KirkD Using Fedora 26 29th September 2008 12:37 AM
internal compiler error: Bus error maxcell Using Fedora 0 26th March 2007 07:49 AM
Can't start error due to some internal error nystom Using Fedora 0 25th September 2006 10:26 PM


Current GMT-time: 16:34 (Wednesday, 20-08-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat