From: Alex Romanenko <alex@vmware.com>
To: Olga Kornievskaia <aglo@umich.edu>,
Michael Wakabayashi <mwakabayashi@vmware.com>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"SteveD@redhat.com" <SteveD@redhat.com>
Subject: RE: NFSv4: Mounting NFS server which is down, blocks all other NFS mounts on same machine
Date: Wed, 9 Jun 2021 20:19:52 +0000 [thread overview]
Message-ID: <CO1PR05MB7925DC61979C2611A3E23721BF369@CO1PR05MB7925.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAN-5tyFZNzyr0FBUeuOc92xiaq+52G1uyfuP3mAZbGxR+v1Rfg@mail.gmail.com>
> There are no SYNs to 2.2.2.2 in my traces. So something different
> about network infrastructures where in your case for some reason you
> are sending something to 2.2.2.2 and the only reason I can think of is
> that you have something in the ARP cache and I don't. And Alex yes I
> do have an ARP entry for my default gateway but no there is no SYN
> sent to the server from a different subnet.
Hi Olga,
Thanks for working with us on this issue.
I think we might have figured out the difference. 2.2.2.2 is inaccessible
public internet address. Does your network have a route to the internet?
That said, for the SYN to be sent the client's network needs to have a route
to the server's network. So, perhaps you can try a test with an IP that you
know your client network has a route for, but is down/unreachable.
P.S. We do see that Trond put out a possible patch for the issue:
https://marc.info/?l=linux-nfs&m=162326359818467&w=2
next prev parent reply other threads:[~2021-06-09 20:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 1:37 NFSv4: Mounting NFS server which is down, blocks all other NFS mounts on same machine Michael Wakabayashi
2021-05-19 19:15 ` Olga Kornievskaia
2021-05-20 9:51 ` Michael Wakabayashi
2021-05-20 10:43 ` Michael Wakabayashi
2021-05-20 23:51 ` Olga Kornievskaia
2021-05-21 19:11 ` Michael Wakabayashi
2021-05-20 18:42 ` Steve Dickson
[not found] ` <CO1PR05MB8101FD5E77B386A75786FF41B7299@CO1PR05MB8101.namprd05.prod.outlook.com>
2021-05-21 19:35 ` Olga Kornievskaia
2021-05-21 20:31 ` Michael Wakabayashi
2021-05-21 21:06 ` Olga Kornievskaia
2021-05-21 22:08 ` Trond Myklebust
2021-05-21 22:41 ` Olga Kornievskaia
2021-06-08 9:16 ` Michael Wakabayashi
2021-06-08 16:10 ` Olga Kornievskaia
2021-06-09 5:31 ` Michael Wakabayashi
2021-06-09 13:50 ` Olga Kornievskaia
2021-06-09 20:19 ` Alex Romanenko [this message]
2021-06-11 5:26 ` Michael Wakabayashi
2021-06-09 14:31 ` Benjamin Coddington
2021-06-09 14:41 ` Olga Kornievskaia
2021-06-09 17:14 ` Michael Wakabayashi
2021-06-09 14:41 ` Trond Myklebust
2021-06-09 15:00 ` Benjamin Coddington
2021-06-09 15:19 ` Trond Myklebust
2021-06-09 6:46 ` Alex Romanenko
2021-05-21 22:38 ` Olga Kornievskaia
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=CO1PR05MB7925DC61979C2611A3E23721BF369@CO1PR05MB7925.namprd05.prod.outlook.com \
--to=alex@vmware.com \
--cc=SteveD@redhat.com \
--cc=aglo@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=mwakabayashi@vmware.com \
--cc=trondmy@hammerspace.com \
/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.