Hi everyone,

I would like to share an issue we encountered from months.

While we copy a file through nfs and we compare md5, it could happen they are not the same.

It results with drop when this file is a video file for example.

The same copy through samba works (same md5) but is muuuuch longer.

I'm just wondering if one of you would know the “room for manoeuvre” I have with nfs parameters to try to resolve this issue.

I am, of course, at your disposal if someone need additional information (setup, cli results, etc.)

Every ideas, tracks, magic potion are welcome

Thank you for your precious help

Best,

Pierre

Context

OneFS version

isi-tvs-1-1# isi version

Isilon OneFS v6.5.5.10 B_6_5_5_138(RELEASE): 0x605050000A0008A:Mon Aug 27 16:20:22 PDT 2012    root@fastbuild-02.west.isilon.com:/build/mnt/obj.RELEASE/build/mnt/src/sys/IQ.amd64.release

NFS settings

Environment

Computer for copying are Apple computer.

Several macOS > same issue (from 10.6.8 to 10.10.2)

NFS chosen for performance in comparison with samba.

For some macs, we follows Isilon considerations regarding nfs, namely :

nfs.conf

nfs.client.mount.options=nfssvers=3,tcp,async,nolock,rw,rdirplus,rsize=65536,wsize=65536

sysctl.conf

net.tcp.delayed_ack=0

net.inet.tcp.recvspace=131072

net.inet.tcp.sendspace=131072

For some others, freshly reinstalled, we don’t.

Whatever theses parameters, the issue comes, randomly, most often on big files.

NB : nfs copy run and finishe without error