[ELDK] Mount NFS problem

[Zaahir Khan]

Hi Detlev,

Thanks for your support.

I am trying to make my PC as the NFS client and sequoia board as the NFS
server.

For testing the NFS  server, in future some other sequoia boards will be
client instead of PC.


Mounting problem got solved.......

none                    /proc/fs/nfsd   nfsd    auto,defaults   0 0

I added the above line to server /etc/fstab .

This line was already there in client fstab.

May be helpful to somebody  facing the same problem.


Thanks & regards,

Zaahir Khan


On Tue, Jun 23, 2009 at 10:47 PM, Detlev Zundel <dzu at denx.de> wrote:

> Hi Zaahir,
>
> > Problem is unable to get the NFS mount
>
> One thing I really would try is to use a different PC instead of the
> sequoia to make sure the server side is ok.
>
> > (Sequoia board)  Server IP  192.168.1.101
> > (PC)                  Client  IP   192.168.1.10
>
> You switch terminology here - I presume the PC is the NFS server and
> sequoia is the client "mounting" the file system.  Wow, this is
> confusing - is it correct that your server, i.e. the PC has the IP
> 192.168.1.101?  Please only list the IPs of the boards, not any IPs of
> "network targets"...
>
> > *All server releated  ::::*
> >
> >
> > #/etc/export file
> > /opt/eldk     192.168.1.10(rw,no_root_squash,sync)
>
> Well now I'm having a problem, because I don't know if the PC is the
> server also in your terminology - but if it is and if your chart above
> is right, then this exports the NFS only to the server itself.  You
> should change it to either 192.168.1.0/255.255.255.0 for the whole
> subnet or at least to the correct IP of sequoia.
>
> > #mii-tool
> > eth0: negotiated 100baseTx-FD, link ok
> >
> > #arp -a
> > ? (192.168.1.10) at 00:50:FC:EB:FF:F2 [ether] on eth0
> >
> > #rpcinfo -p
> >    program vers proto   port
> >     100000    4   tcp    111  portmapper
> >     100000    3   tcp    111  portmapper
> >     100000    2   tcp    111  portmapper
> >     100000    4   udp    111  portmapper
> >     100000    3   udp    111  portmapper
> >     100000    2   udp    111  portmapper
> >     100000    4     0    111  portmapper
> >     100000    3     0    111  portmapper
> >     100000    2     0    111  portmapper
> >     100021    1   udp  38836  nlockmgr
> >     100021    3   udp  38836  nlockmgr
> >     100021    4   udp  38836  nlockmgr
> >     100003    2   udp   2049  nfs
> >     100003    3   udp   2049  nfs
> >     100003    4   udp   2049  nfs
> >     100021    1   tcp  43728  nlockmgr
> >     100021    3   tcp  43728  nlockmgr
> >     100021    4   tcp  43728  nlockmgr
> >     100003    2   tcp   2049  nfs
> >     100003    3   tcp   2049  nfs
> >     100003    4   tcp   2049  nfs
> >     100005    1   udp  58209  mountd
> >     100005    1   tcp  44235  mountd
> >     100005    2   udp  58209  mountd
> >     100005    2   tcp  44235  mountd
> >
> >
> >
> > #exportfs
> > /opt/eldk       192.168.1.10
> >
> > #showmount -e 192.168.1.101
> > Export list for 192.168.1.101:/opt/eldk 192.168.1.10
> >
> >
> >
> > *All client releated :::*
> >
> >
> > #/etc/fstab
> > 192.168.1.101:/opt/eldk          /root/NFSfs    nfs
> > nfsvers=3,rw              0 0
>
> If you do mounts manually, you don't need an fstab entry at all.  This
> is only used for "mount -a".
>
> > #showmount -e 192.168.1.101
> > Export list for 192.168.1.101:/opt/eldk 192.168.1.10
> >
> > #rpcinfo -p
> >    program vers proto   port
> >     100000    2   tcp    111  portmapper
> >     100000    2   udp    111  portmapper
> >     100024    1   udp  32771  status
> >     100024    1   tcp  35158  status
> >
> > #mii-tool
> > eth0: negotiated 100baseTx-FD flow-control, link ok
> > eth1: negotiated 100baseTx-FD, link ok
> >
> >
> > #arp -a
> > ? (211.63.81.60) at 00:1A:4D:67:A5:56 [ether] on eth0
> > ? (211.63.81.1) at 00:0E:E8:8B:73:8B [ether] on eth0
> > ? (192.168.1.101) at 00:10:EC:01:05:E1 [ether] on eth1
> > ? (211.63.81.100) at 00:11:D8:55:3C:69 [ether] on eth0
> >
> >
> >
> > All I am getting
> >
> > On server
> >
> > var/log/message
> > 16]: authenticated mount request from 192.168.1.10:618 for /opt/eldk
> > (/opt/eldk)
> >
> > And client
> >
> > When trying to mount NFS getting
> >
> > mount -o nolock -t nfs 192.168.1.101:/opt/eldk /root/NFSfs
> > mount: 192.168.1.101:/opt/eldk failed, reason given by server:
> Permission
> > denied
>
> Well this sounds pretty obvious - Somehow the export entry does not
> allow the sequoia board to mount the directory.  As mentioned try this
> in /etc/exports on your PC and then work out the difference (maybe the
> missing netmask is a real bummer?!?):
>
> /opt/eldk       192.168.1.0/255.255.255.0(rw,no_root_squash,sync)<http://192.168.1.0/255.255.255.0%28rw,no_root_squash,sync%29>
>
> Cheers
>  Detlev
>
> --
> Or go for generality ... Add a programming language for extensibility
> and write part of the program in that language.
>                                    --- GNU Coding Standards
> --
> DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
>