From: "Cyril B." <cbay@excellency.fr>
To: Ian Kent <raven@themaw.net>, autofs@vger.kernel.org
Subject: Re: Regular deadlocks
Date: Thu, 28 Jul 2016 09:36:01 +0200 [thread overview]
Message-ID: <e9e8fbbc-4722-ffd6-b139-7c1f1107748b@excellency.fr> (raw)
In-Reply-To: <4df27a99-1834-c8be-74d6-f7bdb17df724@excellency.fr>
On 07/01/2016 09:48 AM, Cyril B. wrote:
>> Is there a reason you need to use the nfsv4 root namespace rather than
>> using the
>> /home export directly?
>
> You mean get rid of the bind mounts and have /home/foo be a NFSv4 mount
> to (e.g.) http12:/foo?
>
> If so, I assumed that it would mean having a lot of independant mounts
> over NFS (and as many TCP connections between the NFS client and
> server), and doing a single NFS mount with local bind mounts would be
> better.
>
> However, my assumption may very well be wrong. Would the kernel share
> the same underlying NFS mount (and TCP connection) for all those mount
> points to the same NFS server?
Well, I've been doing that for the past month and everything works
rather flawlessly. In particular, deadlocks are gone, so I'll keep that
setup.
--
Cyril B.
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2016-07-28 7:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 23:41 Regular deadlocks Cyril B.
2016-06-26 1:59 ` Ian Kent
2016-06-26 10:02 ` Cyril B.
2016-06-26 10:30 ` Ian Kent
2016-06-26 11:13 ` Cyril B.
2016-06-27 0:26 ` Ian Kent
2016-06-27 0:35 ` Ian Kent
2016-06-27 14:04 ` Cyril B.
2016-06-28 0:27 ` Ian Kent
2016-06-28 7:48 ` Cyril B.
2016-07-01 7:28 ` Ian Kent
2016-07-01 7:48 ` Cyril B.
2016-07-28 7:36 ` Cyril B. [this message]
2016-06-29 12:45 ` Cyril B.
2016-07-01 7:03 ` Ian Kent
2016-06-26 10:59 ` Ian Kent
2016-06-26 11:02 ` Ian Kent
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=e9e8fbbc-4722-ffd6-b139-7c1f1107748b@excellency.fr \
--to=cbay@excellency.fr \
--cc=autofs@vger.kernel.org \
--cc=raven@themaw.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).