NFS Problem

[Sanjay Shinde]

Hi,
set-up :- NFS server Linux 7.2 box ( Compaq ) exported one file system on HP L-Class server (HP-UX 11.0) example host1:/nfs5 nfs /abc

Problem :- I am trying to copy big file approx 2 GB to host1, example #cp big.file /abc/junkfile

file get copy to nfs server from local machin, but it gives following message in syslog.log on my local_host( HP L class server )
Error-
Mar 19 15:02:59 local_host vmunix: NFS server host1 not responding still trying
Mar 19 15:02:59 local_host vmunix: NFS server host1 ok
Mar 19 15:03:06 local_host vmunix: NFS server host1 not responding still trying
Mar 19 15:03:06 local_host vmunix: NFS server host1 ok

Do I need to check/tune on Linux server side ? As I am new linux side, can you help please

Due to this coping process take more time.

Thanks
Sanjay

[John Carr_2]

Hi


try getting the a small file to copy first as there are other implications with files over 2GB in size.

checkout also the response time to ping you may be timing out.


good luck
John.

[Sanjay Shinde]

Thanks John,
Small file it copies fast and there is no message in syslog.log Also ping works fine below 0. ms

Sanjay

[Sandip Ghosh]

For copyiny the largefile in the HP Server you have to have the filesystem created and mounted as largefiles. But it seems nfs is having some problem. If you don't copy then also it gives the same message in the Syslog.log file?

Sandip

[Sanjay Shinde]

message is only getting when trying to copy large file form local to nfs mounted file system. for small file it does not,
The /etc/exports on nfs ( linux) server as
below
/nfs5 146.184.31.11(rw)

Sanjay

[pap]

Hi Sanjay it seems that your maximum number of packets are dropped. Some of the time your NFS server is not approchable by HP client machine. This may be due to heavy network traffic in contrast to your LAN speed.

You are loosing the connections to NFS server. You need to set some mount parameters while mounting those file systems to HP machine. You need not to change anything from Server side (Linux).

1. Try to increase or double the time our option "timeo"
Keep it at 25 or 30.
2. Check how many nfs daemons are running on Linux server. If it is less than 4 then make it to 4.
3. decrease the size of read buffers and write buffers.
set as below :

rsize=1024
wsize=1024

rsize = read buffer size.
wsize= write buffer size.

4. Also if you are copying the file which is more than 2 GB on size just confirm that Linux machine supports such a large file in his filesystem?

I think now, everything should be OK with your problem.

Let us know if your problem persists furher.

-pap

[pap]

Hi ,
The mount options you can give in the command line whenever you are mounting the file system.

e.g

mount -F nfs rsize=1024 wsize=1024 timeo=30 sysA:/sysA /sysBdir

This will serve your purpose.

Thanks,

-pap

[Mark Vollmers]

Sanjay-

This really doesn't sovle the problem, just side-steps it, but can you ftp over and get the file (from either box)? I don't think that ftp cares about file size. Just a thought.

Mark

[Sanjay Shinde]

By changeing different block size, it shows slight different in performance but it's doesn't solve my problem, but it did dispaer thar error message from syslog.log when I use read/write size below 8K,
Now I decied to go for separate NIC card for both side like server and client side and it improved performance with even 8K ( there is no error message)

Thanks guys for help.