(I'm not subscribed, so please CC me on any replies) I seem to have hit a NFS bug while upgrading a machine from Debian Etch to Debian Lenny. I have a NFS server running FreeBSD 7.0 RC1 and a bunch of clients running Linux. The ones running kernel 2.6.18 work perfectly, as do the ones running 2.6.24. The one I upgraded to 2.6.26 fails. After 5-15 minutes of working normally the mount dies and I get the usual "nfs: server <server> not responding, still trying" in dmesg. The only way I have found to get the mount back is umount -f && mount, waiting does not bring it back. I have tested quite a bunch of different kernel versions, and starting from 25 and ending at the git tree last week they all fail in the same way. Bisecting tracks the problem to commit e06799f958bf7f9f8fae15f0c6f519953fb0257c I originally thought that it was the same as bug 11154, but the patches attached to that bug do not fix this issue. Any thoughts, patches, ideas? -- Arto Jantunen -- 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
