(I found the saved draft of the answer I thought I had send; I send it just for completeness's sake.)
------------------------ Nils Goroll <[EMAIL PROTECTED]> writes: > What happens if you use the noac NFS mount option on the client? That does not seem to change the behaviour. (I have not tried it with this test setup, but it happens with noac in the "real" scenario, too.) > I'd not recommend to use it for production environments unless you > really need to, but this looks like a nfs client caching issue. The "real" scenario is indeed a production environment, but with very low traffic, so we thought noac ould be an options. > Is this an nfsv3 or nfsv4 mount? What happens if you use one or the other? This is v3; I have not yet tried v4 yet. We don't have v4 in use for reasons I don't know (but which I am sure exist and are valid for our environment). > Please provide nfsstat -m output. /mnt/nfsw from repltarget:/pool1/nfsw/.zfs/snapshot Flags: vers=3,proto=tcp,sec=sys,hard,intr,link,symlink,acl,rsize=32768,wsize=32768,retrans=5,timeo=600 Attr cache: acregmin=3,acregmax=60,acdirmin=30,acdirmax=60 ------------------------ As mentioned in the previous post, the problem is no longer an issue for me. Still I'd be curious to here more about it if something turns up. Regards, Juergen. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
