Re: Hard to debug NFS loss of connectivity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Sep 06, 2013 at 05:57:21PM +0200, Emmanuel Florac wrote:
> Le Thu, 5 Sep 2013 17:40:02 -0400
> "J. Bruce Fields" <bfields@xxxxxxxxxxxx> écrivait:
> 
> > I was asking about the on-the-wire errors and getattr replies here,
> > not the application system calls.
> > 
> 
> OK, I've done the dump; I've kept just the last few working calls, then
> the failure calls, and filtered for NFS traffic (there are SSH and
> LACP frames interspersed here). I have absolutely no idea about what's
> going on there :) Any light from the network savvy?

Weird.  Things look normal up through frame 14, which is a READDIRPLUS
reply.  Then the server resends the reply after .2s, and and the client
resends its call shortly thereafter (but without acking the latest
reply).  And then the rest of the trace is resends of the reply.

So it looks like the client stopped ACKing the server's replies?

You may also have filtered out some TCP ACKs, which makes this harder to
work out.

Looks like a networking problem, but I don't know.

--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




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux