On Mon, Mar 12, 2012 at 12:20:17PM -0400, Nikolaus Rath wrote: > Nikolaus Rath <Nikolaus-BTH8mxji4b0@xxxxxxxxxxxxxxxx> writes: > > The problem is that as soon as more than three clients are accessing the > > NFS shares, any operations on the NFS mountpoints by the clients hang. > > At the same time, CPU usage of the VPN processes becomes very high. If I > > run the VPN in debug mode, all I can see is that it is busy forwarding > > lots of packets. I also ran a packet sniffer which showed me that 90% of > > the packets were NFS related, but I am not familiar enough with NFS to > > be able to tell anything from the packets themselves. I can provide an > > example of the dump if that helps. > > I have put a screenshot of the dump on > http://www.rath.org/res/wireshark.png (the full dump is 18 MB, and I'm > not sure which parts are important). Looks like they're doing SETCLIENTID, SETCLIENTID_CONFIRM, OPEN, OPEN_CONFIRM repeatedly. > Any suggestions how I could further debug this? Could the clients be stepping on each others' state if they all think they have the same IP address (because of something to do with the VPN networking?) It'd be interesting to know the fields of the setclientid call, and the errors that the server is responding with to these calls. If you look at the packet details you'll probably see the same thing happening over and over again. Filtering to look at traffic between server and one client at a time might help to see the pattern. --b. -- 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
