Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-17 Thread J. Bruce Fields
On Thu, Aug 16, 2012 at 09:34:24PM +, Jamie Heilman wrote: > J. Bruce Fields wrote: > > On Thu, Aug 16, 2012 at 04:42:08PM -0400, J. Bruce Fields wrote: > > > Hm, weird. In the good case the cb_recall's done with auth_unix, in the > > > bad case with auth_null. OK, that should be enough to

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-17 Thread J. Bruce Fields
On Thu, Aug 16, 2012 at 09:34:24PM +, Jamie Heilman wrote: J. Bruce Fields wrote: On Thu, Aug 16, 2012 at 04:42:08PM -0400, J. Bruce Fields wrote: Hm, weird. In the good case the cb_recall's done with auth_unix, in the bad case with auth_null. OK, that should be enough to go on

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread Jamie Heilman
J. Bruce Fields wrote: > On Thu, Aug 16, 2012 at 04:42:08PM -0400, J. Bruce Fields wrote: > > Hm, weird. In the good case the cb_recall's done with auth_unix, in the > > bad case with auth_null. OK, that should be enough to go on > > > > Thanks for digging into this! > > This should fix

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread J. Bruce Fields
On Thu, Aug 16, 2012 at 04:42:08PM -0400, J. Bruce Fields wrote: > Hm, weird. In the good case the cb_recall's done with auth_unix, in the > bad case with auth_null. OK, that should be enough to go on > > Thanks for digging into this! This should fix it--could you confirm? --b. commit

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread J. Bruce Fields
On Thu, Aug 16, 2012 at 08:18:38PM +, Jamie Heilman wrote: > J. Bruce Fields wrote: > > On Wed, Aug 15, 2012 at 01:58:54PM +, Jamie Heilman wrote: > > > Jamie Heilman wrote: > > > > I'll try to get full rcpdebug traces on client and server as the delay > > > > is occuring in the hopes that

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread Jamie Heilman
J. Bruce Fields wrote: > On Wed, Aug 15, 2012 at 01:58:54PM +, Jamie Heilman wrote: > > Jamie Heilman wrote: > > > I'll try to get full rcpdebug traces on client and server as the delay > > > is occuring in the hopes that helps pin things down, and post them > > > separately. > > > > OK, here

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread Jamie Heilman
J. Bruce Fields wrote: On Wed, Aug 15, 2012 at 01:58:54PM +, Jamie Heilman wrote: Jamie Heilman wrote: I'll try to get full rcpdebug traces on client and server as the delay is occuring in the hopes that helps pin things down, and post them separately. OK, here are the logs

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread J. Bruce Fields
On Thu, Aug 16, 2012 at 08:18:38PM +, Jamie Heilman wrote: J. Bruce Fields wrote: On Wed, Aug 15, 2012 at 01:58:54PM +, Jamie Heilman wrote: Jamie Heilman wrote: I'll try to get full rcpdebug traces on client and server as the delay is occuring in the hopes that helps pin

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread J. Bruce Fields
On Thu, Aug 16, 2012 at 04:42:08PM -0400, J. Bruce Fields wrote: Hm, weird. In the good case the cb_recall's done with auth_unix, in the bad case with auth_null. OK, that should be enough to go on Thanks for digging into this! This should fix it--could you confirm? --b. commit

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread Jamie Heilman
J. Bruce Fields wrote: On Thu, Aug 16, 2012 at 04:42:08PM -0400, J. Bruce Fields wrote: Hm, weird. In the good case the cb_recall's done with auth_unix, in the bad case with auth_null. OK, that should be enough to go on Thanks for digging into this! This should fix it--could you

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread J. Bruce Fields
On Wed, Aug 15, 2012 at 01:58:54PM +, Jamie Heilman wrote: > Jamie Heilman wrote: > > I'll try to get full rcpdebug traces on client and server as the delay > > is occuring in the hopes that helps pin things down, and post them > > separately. > > OK, here are the logs from client and server,

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread Jamie Heilman
Jamie Heilman wrote: > I'll try to get full rcpdebug traces on client and server as the delay > is occuring in the hopes that helps pin things down, and post them > separately. OK, here are the logs from client and server, where a run of my test program under strace -T resulted in:

v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread Jamie Heilman
I really wish I could have nailed this down better, but I've had a hard time reliably reproducing the problem during bisection, and I haven't seen anyone report a similar sounding problem. Here's what I've seen: since 3.5 I've been having spurious delays on my nfs clients, noticable particularly

v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread Jamie Heilman
I really wish I could have nailed this down better, but I've had a hard time reliably reproducing the problem during bisection, and I haven't seen anyone report a similar sounding problem. Here's what I've seen: since 3.5 I've been having spurious delays on my nfs clients, noticable particularly

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread Jamie Heilman
Jamie Heilman wrote: I'll try to get full rcpdebug traces on client and server as the delay is occuring in the hopes that helps pin things down, and post them separately. OK, here are the logs from client and server, where a run of my test program under strace -T resulted in:

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread J. Bruce Fields
On Wed, Aug 15, 2012 at 01:58:54PM +, Jamie Heilman wrote: Jamie Heilman wrote: I'll try to get full rcpdebug traces on client and server as the delay is occuring in the hopes that helps pin things down, and post them separately. OK, here are the logs from client and server, where a