filesystem integration not working (nfs error: success !?)
i tried to use filesystem integration on linux (gentoo) but encountered a very strange error named "success".
#: mount /mnt/wua.la/wuala/direct
mount: mount to NFS server 'localhost' failed: RPC Error: Success.
on that computer a nfs-server is running, so i started wuala using the -noportmapregistration option. btw: can this option be entered somehow into wualarc?
my fstab entry looks like this:
localhost:/wuala /mnt/wua.la/wuala/direct nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183
the check reports portmap and service as ok and volume and integration as failed.
thanks in advance for any hint!
andy
#: mount /mnt/wua.la/wuala/direct
mount: mount to NFS server 'localhost' failed: RPC Error: Success.
on that computer a nfs-server is running, so i started wuala using the -noportmapregistration option. btw: can this option be entered somehow into wualarc?
my fstab entry looks like this:
localhost:/wuala /mnt/wua.la/wuala/direct nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183
the check reports portmap and service as ok and volume and integration as failed.
thanks in advance for any hint!
andy
3
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Summary:
You might have to add the 'tcp' or 'udp' option to your wuala mount line in /etc/fstab:
localhost:/wuala /mnt/wuala nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183,tcp
(Thanks to david for the answer!)
The company says
this answers the question
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Not sure if this will help, but worth a try:
Create a file named /etc/hosts.allow and add these lines:
portmap: 127.0.0.1
lockd: 127.0.0.1
rquotad:127.0.0.1
mountd: 127.0.0.1
statd: 127.0.0.1
Then restart portmap. I had a similar error and this fixed it for me. -
Inappropriate?The entry for the fstab is truncated for me.
If the whole entry is in fstab it works fine.
I’m thankful
-
Inappropriate?what do you think is missing from the entry? try to copy and paste it somewhere else, mark the whole line. it is too long to be displayed correctly.
I’m expecting answers
-
Inappropriate?To copy the whole article in an editor worked for me. But took me hours to realize that in my first try there was missing the rest of the line.
Where did you get the Information howto get thinks working? I didn't find any Information expect of this post.
I’m confident
-
Inappropriate?wua.la -> support -> faq -> technical questions -> fs integration under linux
it still doesn't work for me. everything is set to the faq and the error i get is named 'success'. if that isn't depressing than i doesn't know what is ;-)
well, one day there will be a solution: wuala v2.0 :-)
I’m optimistic
-
Inappropriate?well, thats strange. i used the same settings on a different computer, also gentoo-linux but this time a 64-bit os. also there is no nfs server (and no portmap) running. automatic mount won't work but manual mount works like a charm. it took some time till i found the entry to specify the 32-bit java-vm but now it runs perfectly while on the native 32-bit machine the mounting won't work. both computers run recent software.
I’m confused
-
Inappropriate?I did get the error "mount: mount to NFS server 'localhost' failed: RPC Error: Success." until I added the option tcp (or udp) in /etc/fstab for the wuala mount.
localhost:/wuala /mnt/wuala nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183,tcp
/David -
Inappropriate?Summary:
You might have to add the 'tcp' or 'udp' option to your wuala mount line in /etc/fstab:
localhost:/wuala /mnt/wuala nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183,tcp
(Thanks to david for the answer!)
The company says
this answers the question
-
Inappropriate?On some systems the same symptoms show, if the option nfsvers is not set correctly.
You can execute
rpcinfo -p
on the server to see which versions are aunderstood.
See this debian bug:
http://bugs.debian.org/cgi-bin/bugrep...
"nfsvers=2" worked for me on debian testing/squeeze.
---<(kaimartin)>---
Loading Profile...





