Can you take a perfstat? Take a perfstat during while the file is written to the filer.
And a real quick test of read performance on the filer, is try doing a dump to /dev/null on the filer's console. A quick check of ifstat can check for network interface problems (and netdiag as well). nfs_hist is a good tool to use to check if the filer is taking a long time to respond to nfs calls. If nfs_hist shows the filer responding quickly, then the network may be at fault (I suspect the network, but that' just a hunch right now). What release are you running? 6.5.x has a whole slew of problems that can really bog down nfs performance, especially if you use DNS names. A slow dns server can cause many problems for nfs access in 6.5. Checking nfsstat -d will show you lots of detailed nfs statistics that may be of no use for you, but may at least keep you entertained while troubleshooting the problem.
Hope that helps, -Blake
On 9/12/05, Barry Robison barryr@al.com.au wrote:
Just a short response that could be longer but.. we often see writes that are a lot faster than reads because of the cache. You can write to the NetApp at line speed cause all the data is going into the cache and then sycning to disk at its own pace. However reads of non-cached data *must* seek to the data..
As for general nfs performance, could you please post you output of options nfs
cheers, Barry