slow data transfer over nfs ... is it fedora?

[Samuel Flory]

Harry Putnam wrote:
> Samuel Flory <sflory at rackable.com> writes:
> 
> 
>>Harry Putnam wrote:
>>
>>>I lack much experience with nfs but I suspect I should be seeing much
>>>better transfer rates here.  Wondering if a few posters could post a
>>>timed transfer of know amount of data
>>>This is from a rh9 to yarrow (fully updated)  I'll show exports file
>>>at the end:
>>>   root # du -sh $rea/News/agent/nntp/enews*
>>>  169M    /home/reader/News/agent/nntp/enews.newsguy.com
>>>   root # time cp -a  $rea/News/agent/nntp/enews*/ /EXP_root
>>>  real    12m26.120s
>>>  user    0m0.340s
>>>  sys     0m13.990s
>>>So 169MB in 12 1/2 minutes.
>>>cat /etc/exports:
>>>  /                        reader(rw,async,insecure_locks,no_root_squash)
>>>  /home                    reader(rw,async,insecure_locks,no_root_squash)
>>>  /var                     reader(rw,async,insecure_locks,no_root_squash)
>>>  /mnt/exp                 reader(rw,async,insecure_locks,no_root_squash)
>>>  /usr                     reader(rw,async,insecure_locks,no_root_squash)
>>>  /tmp                     reader(rw,async,insecure_locks,no_root_squash)
>>>
>>
> 
> First do you have example speeds?
> 
> 
>>   What does /proc/mount say?  
> 
> Nothing here:
> cat /proc/mount No such file or directory
> 
>>What does "mii-tool eth0" or "ethtool
>>   eth0" say?  Are you dropping packets? (ifconfig and ping )
> 
> 
>   root # mii-tool
>   eth0: negotiated 100baseTx-HD, link ok
>   eth1: no link
> ==================================
>    root # ethtool eth0
>   Settings for eth0:
>         Supported ports: [ TP MII ]
>         Supported link modes:   10baseT/Half 10baseT/Full 
>                                 100baseT/Half 100baseT/Full 
>         Supports auto-negotiation: Yes
>         Advertised link modes:  10baseT/Half 10baseT/Full 
>                                 100baseT/Half 100baseT/Full 
>         Advertised auto-negotiation: Yes
>         Speed: 100Mb/s
>         Duplex: Half
>         Port: Twisted Pair
>         PHYAD: 1
>         Transceiver: internal
>         Auto-negotiation: on
>         Supports Wake-on: puag
>         Wake-on: g
>         Link detected: yes
> 
> ifconfig reading taken during write across nfs:
>    root # ifconfig eth0
>   eth0      Link encap:Ethernet  HWaddr 00:03:47:FA:4B:13  
>           inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2023545 errors:50 dropped:0 overruns:0 frame:50
>           TX packets:1867748 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:6765 txqueuelen:100 
>           RX bytes:983047766 (937.5 Mb)  TX bytes:454217274 (433.1 Mb)
>           Interrupt:11 Base address:0xdf00 Memory:ff9fc000-ff9fc038 
> 
> To my inexperienced eye those look normal.. are they?
> 

   The errors are not normal, but there are not very many of them. 
Certainly not enough examplain your nfs speed.  Try switching to tcp v3 
mount, and seeing if that improves things. "man mount"
-- 
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory  <sflory at rackable.com>