On Fri, 19 Mar 2010 10:21:57 +0800, Bian Naimeng wrote: > > After upgrading my server (kernel 2.6.19 to 2.6.33, nfs-utils 1.1.0 > > to 1.2.1/1.1.4/1.1.6), and probably other stuff too), and possibly > > my client laptop's kernel, I have suddenly started to get these > > "server X not responding, timed out" errors (on my client), > > especially (only?) when doing large file transfers. This would lead > > to input/output errors, and the transfers would fail. > > > > I never noticed any such problems for over two years, using the > > older versions. The networking (wifi link) hasn't changed. > > > > Usually the file transfer trips and falls over itself near the end > > -- Ie. it will do 600MB out of 800MB just fine, and then suddently > > start giving these "timed out" errors, and then crash and burn. At > > this point, I am forced to "umount -fl" the mount. If I then try to > > remount it, the server acnowledges my "authenticated mount > > requests" perfectly fine, but my client (laptop) still appears > > "hung". After a few minutes, I am able to remount it. > > > > I tried playing with the rsize/wsize/timeo/retrans variables, but > > none of it seemed to fix the problem. > > > > Any ideas about what has changed? Maybe this is/was a well-known > > problem? :P > > > > I do not know the what's the reason. And I am not sure the followed > discussion can fix this problem, but maybe it can help you. > http://marc.info/?l=linux-nfs&m=123478426412524&w=2 Both the patches mentioned in that thread already seem to have been applied to my kernels. So, although the problem seems related, it wasn't that bug in particular. The person in that thread was talking about mounts dying after 5-15minutes, which doesn't happen with me -- my problem only seems to occur under intense activity. -- 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
