maemo.org - Talk - nfs mount troubles

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)

- - nfs mount troubles (https://talk.maemo.org/showthread.php?t=41929)

nfs mount troubles

hi there,

i'm trying to get my nfs share mounted on my n900 but keep running into errors. my export on the server reads:

Code:

/on_ice 192.168.1.0/24(rw,sync)

i mount with:

Code:

mount -t nfs 192.168.1.102:/on_ice /on_ice

and receive the error:

Code:

mount: mounting 192.168.1.102:/on_ice on /on_ice failed: Input/output error

i have a desktop that mounts the same nfs share with no problems.

anybody have any ideas whats going wrong?
thanks

Re: nfs mount troubles

you will need to install portmap as well (apt-get install portmap)

NFS started working when I did this.

Re: nfs mount troubles

portmap was alleady installed when doing the above

Code:

 apt-get install portmap

Reading package lists... Done

Building dependency tree       

Reading state information... Done

portmap is already the newest version.

portmap set to manually installed.

0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Re: nfs mount troubles

if you've rebootet the phone after installing portmap you need to start portmap. it's not startet automatically on boot.

Re: nfs mount troubles

/etc/init.d/portmap start
Starting portmap daemon...Already running..

Re: nfs mount troubles

any hints in the syslog from the server?

Re: nfs mount troubles

what would i be looking for?

Re: nfs mount troubles

Did you check hosts.allow and hosts.deny?

Re: nfs mount troubles

theyre both empty.. i take it that means that all hosts are allowed. my desktop mounts the nfs with no problem. so i dont think there are access problems on the server itself.... any more ideas :)

Re: nfs mount troubles

got it working using -o nolock,udp.

anybody able to enlighten me why this works?

Re: nfs mount troubles

Sounds like the problem lies with the nfs lock daemon.
Are you sure it won't work unless you add ",udp"? udp is normally the default for NFS, so with or without -o udp should be the same. The active alternative is -o tcp, to change the default.

Re: nfs mount troubles

I also had problems with this.
I can mount my nfs shares on other systems either with plain nfs or nfs4. The debian server uses by default the portmap option "-i 127.0.0.1", but it doesn't seem to be a problem for the other clients.

On the N900 the are some problems though:
- The portmap daemon won't ever start because for some reason, the init script detects "pidof portmap" as portmap itself so it says "Already running." To get it to start I had to edit the lauch script commenting that line out.
- After that, mounting the share, with "-t nfs" gives a:
"mount: RPC: Unable to receive; errno = Connection refused"
- Editing the portmap conf on the server and removing the "-i 127.0.0.1" limitation makes the error message change to:
"mount: IP:/ failed, reason given by server: Permission denied"
- Trying to mount with NFSv4 always fails with:
"mount: mounting IP:/ on mountpoint failed: Invalid argument". Lack of kernel support?

Finally, the solution for me:
- hack the portmap init script to force it to launch the daemon
- remove the "-i 127.0.0.1" portmap option on the server side
- mount with IP:/path/from/server/root instead of IP:/path/from/share/root as I do on the rest of the computers

This is my first time playing with nfs, but as far as I've read on the Internet, this is some legacy behavior, isn't it?