Comment 28 for bug 1270445

Strange — that’s exactly what I did on the vagrant image, but it
doesn’t fix the problem.. The symptom is that the first time a fs gets
mounted it takes about 10s (presumably time for the kerberos call to
time out) and then it mounts normally. On my non-vm machines (mostly
mint 17), but at least one trusty system, just setting NEED_GSSD=yes
in /etc/default/nfs-common did the trick, no need to blacklist the
kerberos module.

But neither seems to work in the vagrant vm.. perhaps I need to double
check with a stock trusty vm image not using vagrant..

/jamie

On Fri, Dec 5, 2014 at 4:44 AM, Andre <email address hidden> wrote:
> I had to blacklist the module rpcsec_gss_krb5 on all Trusty machines to
> get NFS working at aceptable speeds again. Therefore I added the
> following line:
>
> blacklist rpcsec_gss_krb5
>
> to the following file:
>
> /etc/modprobe.d/blacklist.conf
>
> After a reboot everything was fine. Other comments here describe that
> blacklisting IPV6 would help as well.
>
> I see three options:
> 1) we have all misconfigured our NFS servers (to which the previous Ubuntu releases had a tolerance)
> 2) there is a bug in the pre-configuration of NFS or other modules in Trusty
> 3) there is a bug somewhere in the binaries
>
> Given this bug report over at RedHat:
> https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1001934
> with a link to Linux bugs:
> http://article.gmane.org/gmane.linux.nfs/60081
> indicates that there is/was a bug in the Linux kernel which was then fixed. Did that fix make it into Trusty's kernel?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1270445
>
> Title:
> slow NFS4 without "NEED_GSSD=yes"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1270445/+subscriptions

--
James Mazer
Department of Neurobiology
Yale School of Medicine
phone: 203-737-5853
fax: 203-785-5263
url: http://jackknife.med.yale.edu