[Bulk] Re: Setting up NFS client

[Chris Plasun]

> On Sat, 2009-04-18 at 18:53 +0100, Michael Abbott wrote:
>> On Sat, 18 Apr 2009, Paul Smith wrote:
>>> On Sat, 2009-04-18 at 01:52 -0700, Chris Plasun wrote:
>>>> On the board I run "mount -t nfs 192.168.1.102:/home/na/nfstest 
>>>> /nfstest" but it eventually returns with the following error:
>>>>
>>>> mount: RPC: Timed out
>>>> mount: nfsmount failed: Bad file descriptor
>>>> mount: Mounting 192.168.1.102:/home/na/nfstest on /nfstest failed:
>>>> Bad file descriptor
>>> Also, if you're seeing a delay on the client you probably don't have the
>>> portmapper running on the client.  If you don't want to add it there
>>> that's OK, but then you have to disable lock management; add the "-o
>>> nolock" option to your mount command on the client.
>> This issue, the portmapper, threw me for a long time.  Is it still not 
>> built into busybox?
> 
> I haven't looked.  I just use -o nolock on all my mounts so I don't need
> RPC.  For my purposes I don't need to worry about this.
	>
>> I have to build this separately (and ended up having 
>> to make a couple of tiny patches for out of tree building to work).  I 
>> downloaded portmap-6.0 from http://neil.brown.name/portmap/ .
> 
> Nice; have you send this along upstream?  In my experience people are
> usually happy to get things like this.

***Paul, Ralph, thank you for your help.***

I followed your respective instructions and have verified that NFS works 
on the SUSE virtual box by mounting locally. I was able to read a test 
file in the exported directory.

However, I was unable to get the MPC8313 board to mount, it just hung 
there. I didn't wait for it to return message.

When I started the NFS server the following messages appeared (local 
test worked as mentioned above):


**********
linux-9vtc:~ # rcnfsserver start
Starting kernel based NFS server: idmapdexportfs: No options for
/home/na/nfstest *: suggest *(sync) to avoid warning
exportfs: /etc/exports [1]: Neither 'subtree_check' or
'no_subtree_check' specified for export "*:/home/na/nfstest".
   Assuming default behaviour ('no_subtree_check').
   NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: No host name given with /home/na/nfstest (ro), suggest *(ro)
to avoid warning
exportfs: /etc/exports [1]: Neither 'subtree_check' or
'no_subtree_check' specified for export "*:/home/na/nfstest".
   Assuming default behaviour ('no_subtree_check').
   NOTE: this default has changed since nfs-utils version 1.0.x

exportfs: duplicated export entries:
exportfs:       *:/home/na/nfstest
exportfs:       *:/home/na/nfstest
  mountd statd nfsd sm-notify
********

Are "exportfs: No host name given..." and "exportfs: duplicated export 
entries:" clues?

I ran Wireshark on the Suse virtual box and the following appeared 
(192.168.1.104 is the MPC8313 and 192.168.1.105 is the SUSE virtual box):

********
3	3.764642	192.168.1.104	192.168.1.105	TCP	izm > sunrpc [SYN] Seq=0
Win=5840 Len=0 MSS=1460 TSV=401054 TSER=0 WS=1

4	5.113492	192.168.1.104	192.168.1.105	TCP	tinc > sunrpc [SYN] Seq=0
Win=5840 Len=0 MSS=1460 TSV=401392 TSER=0 WS=1

5	6.761461	192.168.1.104	192.168.1.105	TCP	izm > sunrpc [SYN] Seq=0
Win=5840 Len=0 MSS=1460 TSV=401804 TSER=0 WS=1

6	8.761532	Motorola_00:95:02	CadmusCo_a2:ad:66	ARP	Who has
192.168.1.105?  Tell 192.168.1.104

7	8.761545	CadmusCo_a2:ad:66	Motorola_00:95:02	ARP	192.168.1.105 is at
08:00:27:a2:ad:66

8	12.761716	192.168.1.104	192.168.1.105	TCP	izm > sunrpc [SYN] Seq=0
Win=5840 Len=0 MSS=1460 TSV=403304 TSER=0 WS=1

9	24.761970	192.168.1.104	192.168.1.105	TCP	izm > sunrpc [SYN] Seq=0
Win=5840 Len=0 MSS=1460 TSV=406304 TSER=0 WS=1
********

Any ideas?

Thanks guys.

Chris Plasun