From: bfields@fieldses.org (J. Bruce Fields)
To: Chandler <admin@genome.arizona.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS hangs on one interface
Date: Wed, 23 Oct 2019 13:15:23 -0400 [thread overview]
Message-ID: <20191023171523.GA18802@fieldses.org> (raw)
In-Reply-To: <3447df77-1b2f-6d36-0516-3ae7267ab509@genome.arizona.edu>
Beats me. My first guess would be some kind of networking problem.
Maybe try running wireshark and watching to see if certain calls aren't
getting responses.
--b.
On Tue, Oct 22, 2019 at 05:34:51PM -0700, Chandler wrote:
> Hi all, I'm sure you get this alot, but I couldn't figure out any solution. We have a client/server pair with both 1Gb and 10Gb network interfaces. I can mount the share on the client on the 1Gb interface just fine and interact with it normally. If I unmount and try to mount the share on the 10Gb interface, it will mount but everything after that hangs (like ls or df). The exports entry is the same on the server, i.e.:
>
> #1Gb interface
> /data 10.10.10.0/24(rw,no_root_squash,async)
> #10Gb interface
> /data 128.196.X.X/28(rw,no_root_squash,async)
>
> I turned off iptables for troubleshooting and checked with the NOC here. Using NFSv4 by default and CentOS 6.10 2.6.32 kernel. I had some strange results if i try vers=3 or vers=2, then i can "ls /data" but if I try to "ls /data/subdir" then it hangs again. Now it doesn't even mount if i try with vers=3 or vers=2
>
next prev parent reply other threads:[~2019-10-23 17:15 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 [this message]
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
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=20191023171523.GA18802@fieldses.org \
--to=bfields@fieldses.org \
--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).