From: Jeff Layton <jlayton@redhat.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-nfs@vger.kernel.org
Subject: Re: 4.6, 4.7 slow ifs export with more than one client.
Date: Tue, 06 Sep 2016 18:51:48 -0400 [thread overview]
Message-ID: <1473202308.2505.8.camel@redhat.com> (raw)
In-Reply-To: <3362C9C5-7F87-462C-B1C4-D704B45B84BE@linuxhacker.ru>
On Tue, 2016-09-06 at 12:29 -0400, Oleg Drokin wrote:
> On Sep 6, 2016, at 12:00 PM, Jeff Layton wrote:
> >
> >
> > Shrug...feel free to propose a better scheme for generating unique
> > ids
> > if you can think of one. Unfortunately, there are always cases when
> > these mechanisms for getting a persistent+unique id break down.
> >
> > That's the reason that nfs provides an interface to allow setting a
> > uniquifier from userland via module param.
>
> Fair enough, though I guess module parameter is not really a super
> convenient place
> for it when you run off nfs-root.
> I guess you were not really enticed with the mac address idea too ;)
>
Which mac address? It's not always a given that the host will initialze
them in the same order when you have multiple interfaces, even if the
hardware doesn't change out from under you.
This is just one of those classic "punt the solution to userland" sort
of problems that's just really hard to fix in the kernel in a way that
will always work.
> Anyway, thank you very much for your help, now I have some better
> idea of what's going on and what to try next.
No problem. Diagnosing these sorts of problems can be pretty difficult.
Note too that earlier versions of the client had a length limitation on
this string, which could cause similar problems even when the hostnames
are already set if they were very long names and only differed at the
end. commit 873e385116b2cc5c7daca8f51881371fadb90970 fixes that
problem.
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2016-09-06 22:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 4:55 4.6, 4.7 slow ifs export with more than one client Oleg Drokin
2016-09-06 14:30 ` Jeff Layton
2016-09-06 14:58 ` Oleg Drokin
2016-09-06 15:18 ` Jeff Layton
2016-09-06 15:47 ` Oleg Drokin
2016-09-06 16:00 ` Jeff Layton
2016-09-06 16:29 ` Oleg Drokin
2016-09-06 22:51 ` Jeff Layton [this message]
2016-09-06 16:38 ` Chuck Lever
2016-09-06 18:52 ` Oleg Drokin
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=1473202308.2505.8.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=green@linuxhacker.ru \
--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 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.