All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: Hard to debug NFS loss of connectivity
Date: Fri, 6 Sep 2013 13:15:17 -0400	[thread overview]
Message-ID: <20130906171517.GA26256@umich.edu> (raw)
In-Reply-To: <20130906175721.30082c11@harpe.intellique.com>

Emmanuel Florac wrote:

  Le Thu, 5 Sep 2013 17:40:02 -0400
  "J. Bruce Fields" <bfields@fieldses.org> é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?

I suggest you filter on port=2049 instead of proto=nfs.

  parent reply	other threads:[~2013-09-06 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 17:18 Hard to debug NFS loss of connectivity Emmanuel Florac
2013-09-05 20:45 ` J. Bruce Fields
2013-09-05 21:34   ` Emmanuel Florac
2013-09-05 21:40     ` J. Bruce Fields
2013-09-06 15:57       ` Emmanuel Florac
2013-09-06 16:07         ` J. Bruce Fields
2013-09-06 16:55           ` Emmanuel Florac
2013-09-10 13:28             ` J. Bruce Fields
2013-09-10 13:34               ` Emmanuel Florac
2013-09-06 17:15         ` Jim Rees [this message]
2013-09-11 15:11 ` Hard to debug NFS loss of connectivity: problem solved Emmanuel Florac
2013-09-11 20:14   ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130906171517.GA26256@umich.edu \
    --to=rees@umich.edu \
    --cc=bfields@fieldses.org \
    --cc=eflorac@intellique.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.