[Note that I'm not replying to the list. I usually don't.]
This is a common error one sees when copying over a large file.
My experience has been that changing the rsize/wsize parameters
to 32K usually helps. But to be honest, it really depends on your
network. What I usually do is run iozone and use those settings
for my NFS mount points.
Here's something which might also help:
http://tldp.org/HOWTO/NFS-HOWTO/performance.html
Good luck,
-dwight-
On Monday 06 November 2006 14:46, Sue Sivets wrote:
> I'm getting what look like transmission error messages while the
> sles10 installation system is being transferred from my linux pc to
> the mainframe. It seems like it was eons ago as far as my memory
> goes, but I think I remember getting something similar when I
> installed sles9. Can anyone shed any light on what's happening, and
> what I can do to fix it? The messages are:
>
> nfs: server 192.168.150.108 not responding, still trying
> nfs: server 192.168.150.108 OK
>
> It took over an hour and a half to transfer the sles10 installation
> system using NFS, and then it crumbled and died after I logged on
> using ssh and invoked yast. I'm in the middle of transferring it
> again, but I'd just as soon not have to wait that long every time I
> use NFS.
>
> Sue
>
> --
> Suzanne Sivets
> Systems Programmer
> Innovation Data Processing
> 275 Paterson Ave
> Little Falls, NJ 07424-1658
> 973-890-7300
> Fax 973-890-7147
> [EMAIL PROTECTED]
>
> -------------------------------------------------------------------
>--- For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO
> LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
