From: Olga Kornievskaia <aglo@umich.edu>
To: Chandler <admin@genome.arizona.edu>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS hangs on one interface
Date: Mon, 11 Nov 2019 10:46:05 -0500 [thread overview]
Message-ID: <CAN-5tyGD3hNcG7=+xdB4Bs1OCCUoLzZ5ocsJusuxd3n3+x=7gw@mail.gmail.com> (raw)
In-Reply-To: <49472814-8dcd-4594-d48e-be4c1d9a8d8f@genome.arizona.edu>
Hi Chandler,
Given what you say, it sounds to me more like a generic networking
issue between this particular problem and the server.
debug messages are logging that client can't reach the server:
Nov 8 17:58:21 NFSclient kernel: nfs: server x.2 not responding, still trying
I'd recommend making sure that your network works alright between
those interfaces. Perhaps running an iperf for a few minutes to make
sure you are seeing expected, consistent performance between those two
nodes. Another thing to check if you for some reason have duplicate
IPs in the system that can show up as weird hangs.
On Fri, Nov 8, 2019 at 8:22 PM Chandler <admin@genome.arizona.edu> wrote:
>
> Hi Olga, thanks so much for your help.
>
> I tried to reboot and still having weird issues. If I mount over the local network (10.x address) then there are no issues. As soon as I try to mount over the 10G network, weird things happen. For example, I can perform the mount just fine and do "ll /mount" but as soon as I try another directory like "ll /mount/users" then it hangs. Also this only happens between these two machines with 10G interfaces. The server with the 10G interface has several other 1G clients that outside the local 10.x network that connect to it on the 10G interface, and those clients all work fine as well, so seems to be an issue specific to this client on the 10G interface.
>
> In my earlier post, I did try troubleshooting with vers=3 and vers=2 just to see if that was the issue, but since then have been using the defaults (so vers=4).
>
> I turned on the rpcdebug on both client and server with "rpcdebug -m nfs(d) all" but it seemed to lock up the server and i had to reboot it, so will keep that off for now. I attached a log of the debug messages from the client showing what commands I executed (snoopy) and the resulting kernel debug entries, hope this helps. The hangup happens at the end when I ls -l on the users directory. Let me know if there's anything else I can provide.
>
next prev parent reply other threads:[~2019-11-11 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 0:34 NFS hangs on one interface Chandler
2019-10-23 17:15 ` J. Bruce Fields
2019-10-24 23:40 ` Chandler
2019-10-25 0:37 ` Rick Macklem
2019-10-30 6:30 ` Chandler
2019-11-05 0:28 ` Chandler
2019-11-05 16:24 ` Olga Kornievskaia
[not found] ` <49472814-8dcd-4594-d48e-be4c1d9a8d8f@genome.arizona.edu>
2019-11-11 15:46 ` Olga Kornievskaia [this message]
2019-11-12 22:14 ` Chandler
2019-11-20 18:43 ` Chandler
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='CAN-5tyGD3hNcG7=+xdB4Bs1OCCUoLzZ5ocsJusuxd3n3+x=7gw@mail.gmail.com' \
--to=aglo@umich.edu \
--cc=admin@genome.arizona.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).