From: Arno Schuring <aelschuring@hotmail.com>
To: linux-nfs@vger.kernel.org
Subject: Re: sec=krb5 mounts never return
Date: Wed, 26 Oct 2011 00:00:25 +0200 [thread overview]
Message-ID: <20111026000025.64f1e215@neminis.intra.loos.site> (raw)
In-Reply-To: <20111021012327.612839b5@neminis.loos.site>
Arno Schuring (aelschuring@hotmail.com on 2011-10-21 01:23 +0200):
> Hello list,
>
> tl;dr: mount calls with sec=krb5 never return. They appear to get
> stalled in the kernel on "svc: transport is dead". I need to know
> if this is a configuration issue, a kernel problem or a userland
> problem, and how it can be resolved.
This appears to have been reported two months ago against Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638157
And fixed over a year ago on this list:
http://www.spinics.net/lists/linux-nfs/msg14723.html
It's a wonderful world, isn't it?
Best wishes,
Arno
prev parent reply other threads:[~2011-10-25 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 23:23 sec=krb5 mounts never return Arno Schuring
2011-10-21 14:33 ` Kevin Coffman
2011-10-21 20:10 ` Arno Schuring
2011-10-21 20:58 ` Kevin Coffman
2011-10-21 21:43 ` Douglas E. Engert
2011-10-22 11:12 ` Arno Schuring
2011-10-25 22:00 ` Arno Schuring [this message]
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=20111026000025.64f1e215@neminis.intra.loos.site \
--to=aelschuring@hotmail.com \
--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 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 NNTP newsgroup(s).