From: Steve Dickson <SteveD@redhat.com>
To: Luk Claes <luk@debian.org>
Cc: Richard Smits <R.Smits@tudelft.nl>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: gssd mounts not working
Date: Sat, 23 Apr 2011 13:47:58 -0400 [thread overview]
Message-ID: <4DB310CE.4080009@RedHat.com> (raw)
In-Reply-To: <4DB30594.1060704@debian.org>
On 04/23/2011 01:00 PM, Luk Claes wrote:
> On 04/23/2011 02:16 PM, Steve Dickson wrote:
>>
>>
>> On 04/21/2011 02:58 AM, Richard Smits wrote:
>>> Hello,
>>> We are having problems with our gssd nfs mounts. I will explain our situation.
>>>
>>> Our clients are running SLED 11 SP1.
>>> Our server is a Netapp filer with Ontap 7.3.3P4.
>>>
>>> We provide NFS exported directory's with krb5 security.
>>>
>>> Our KDC is a Windows 2003 and 2008 Active Directory.
>>>
>>> If we use nfs-client-1.2.1-8.1 everything works as expected.
>>>
>>> But if we upgrade to (any) newer client, all gssd mounts fail. Now there is a bugreport on Novell Bugzilla about this : https://bugzilla.novell.com/show_bug.cgi?id=614293#c7
>>>
>>> Apperantly if the nfs client is compiled with --disable-tirpc , the ticket size from the AD is to big ?
>> Yes this problem was fixed in libitrpc with:
>>
>> commit 599511589ca7ddb3b2eac8d3aa5b0b38be7a7691
>> Author: Jeff Layton <jlayton@redhat.com>
>> Date: Fri Mar 5 14:27:13 2010 -0500
>>
>> libtirpc: allow larger ticket sizes with RPCSEC_GSS
>
> When will 0.2.2 be released?
I'll try to get it out sometime next week...
steved.
prev parent reply other threads:[~2011-04-23 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 6:58 gssd mounts not working Richard Smits
2011-04-23 12:16 ` Steve Dickson
2011-04-23 17:00 ` Luk Claes
2011-04-23 17:47 ` Steve Dickson [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=4DB310CE.4080009@RedHat.com \
--to=steved@redhat.com \
--cc=R.Smits@tudelft.nl \
--cc=linux-nfs@vger.kernel.org \
--cc=luk@debian.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