> On Jul 31, 2017, at 4:50 PM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > On Mon, 2017-07-31 at 16:28 -0400, Chuck Lever wrote: >> Hi Jeff- >> >> Observed with v4.13-rc[23] during NFSv3 connectation testing. >> The lock test stalls for a minute or two during test #7. >> >> If you haven't already seen this, I can dig deeper. >> >> Jul 31 16:11:08 klimt rpc.mountd[1640]: authenticated mount request from 192.168.2.2:864 for /export/tmp (/export/tmp) >> Jul 31 16:11:28 klimt rpc.mountd[1640]: authenticated unmount request from 192.168.2.2:740 for /export/tmp (/export/tmp) >> Jul 31 16:11:28 klimt rpc.mountd[1640]: authenticated mount request from 192.168.2.2:844 for /export/tmp (/export/tmp) >> Jul 31 16:12:35 klimt kernel: lockd: server manet.1015granger.net not responding, timed out >> Jul 31 16:12:49 klimt rpc.mountd[1640]: authenticated unmount request from 192.168.2.2:989 for /export/tmp (/export/tmp) >> Jul 31 16:12:49 klimt rpc.mountd[1640]: authenticated mount request from 192.168.2.2:844 for /export/tmp (/export/tmp) >> Jul 31 16:13:10 klimt rpc.mountd[1640]: authenticated unmount request from 192.168.2.2:813 for /export/tmp (/export/tmp) >> Jul 31 16:13:10 klimt rpc.mountd[1640]: authenticated mount request from 192.168.2.2:860 for /export/tmp (/export/tmp) >> Jul 31 16:14:25 klimt kernel: lockd: server manet.1015granger.net not responding, timed out >> Jul 31 16:14:30 klimt rpc.mountd[1640]: authenticated unmount request from 192.168.2.2:636 for /export/tmp (/export/tmp) >> Jul 31 16:14:30 klimt rpc.mountd[1640]: authenticated mount request from 192.168.2.2:960 for /export/tmp (/export/tmp) >> Jul 31 16:14:51 klimt rpc.mountd[1640]: authenticated unmount request from 192.168.2.2:884 for /export/tmp (/export/tmp) >> Jul 31 16:14:51 klimt rpc.mountd[1640]: authenticated mount request from 192.168.2.2:822 for /export/tmp (/export/tmp) >> Jul 31 16:17:02 klimt rpc.mountd[1640]: authenticated unmount request from 192.168.2.2:778 for /export/tmp (/export/tmp) >> >> > > That's not anything that I've seen, but I haven't been doing any v3 > testing. Let me know what you find. > > FWIW, the only real file locking change this cycle was a patch from > Christoph to clean up the fcntl getlk/setlk syscalls. lockd hooks in a > bit below that layer so I'd be surprised if that would affect it. Filed https://bugzilla.linux-nfs.org/show_bug.cgi?id=311 to track this issue. -- Chuck Lever -- 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
