You're using a non-default timeo=60 on a TCP connection. Why? > -----Original Message----- > From: linux-nfs-owner@xxxxxxxxxxxxxxx [mailto:linux-nfs- > owner@xxxxxxxxxxxxxxx] On Behalf Of dE . > Sent: Friday, November 23, 2012 6:02 AM > To: linux-nfs@xxxxxxxxxxxxxxx > Subject: Slow NFS loop performance. > > Humm... The last thing I expected was no response even in the mailing list. > > So I'm filing a bug on this. > > On Oct 23, 2012 2:19 PM, "dE ." <de.techno@xxxxxxxxx> wrote: > > Hi! > > > > Great job with NFS server, it surely is fast, but not on loop devices. > > > > If I loop mount a file and share the mount point over NFS3 or NFS4, the > > write performance of the client on the loop mounted share is pretty bad. > > > > On a 100 Mbps (or 12.5MBps) full duplex Ethernet link, I get ~8MBps > > speeds, whereas on the loop mounted device, I get at best 6MBps. > > > > Any ideas why? > > > > My server configuration (NFS4) -- > > > anonuid=1000,anongid=1000,**secure,no_subtree_check,rw,**fsid=0,cross > mnt > > > > My client mount options -- > > rsize=1048576,wsize=1048576,**async,hard,timeo=60,retrans=2,** > > actimeo=900,retry=2,**lookupcache=pos,nfsvers=4,** > > nolock,intr,noacl,rdirplus > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the > body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at > http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
