From: "Benjamin Coddington" <bcodding@redhat.com>
To: "Trond Myklebust" <trondmy@hammerspace.com>
Cc: mwakabayashi@vmware.com, linux-nfs@vger.kernel.org,
aglo@umich.edu, SteveD@redhat.com
Subject: Re: NFSv4: Mounting NFS server which is down, blocks all other NFS mounts on same machine
Date: Wed, 09 Jun 2021 11:00:21 -0400 [thread overview]
Message-ID: <443A6C4D-28EC-4866-B464-6B04EAF1CF4D@redhat.com> (raw)
In-Reply-To: <752114495b47624b022bb7de366c6b1771d0599a.camel@hammerspace.com>
On 9 Jun 2021, at 10:41, Trond Myklebust wrote:
> On Wed, 2021-06-09 at 10:31 -0400, Benjamin Coddington wrote:
>>
>> It's not disputed that mounts waiting on the transport layer will block
>> other mounts.
>>
>> It might be able to be changed: there's this torch:
>> https://lore.kernel.org/linux-nfs/87378omld4.fsf@notabene.neil.brown.name/
>>
>
> No.
>
>> ..or there may be another way we don't have to wait ..
>>
>
> OK. So let's look at how we can solve the problem of the initial
> connection to the server timing out and causing hangs in
> nfs41_walk_client_list(), and leave aside any other corner case
> problems (such as the server going down while we're mounting).
>
> How about something like the following (compile tested only) patch?
It works as intended for this case, but I don't have my head wrapped around
the implications of the change yet.
Ben
next prev parent reply other threads:[~2021-06-09 15:00 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
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 [this message]
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=443A6C4D-28EC-4866-B464-6B04EAF1CF4D@redhat.com \
--to=bcodding@redhat.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.