Re: nfsv3 gssapi client?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sep 17, 2010, at 1:43 PM, J. Bruce Fields wrote:

> On Fri, Sep 17, 2010 at 06:54:35PM +0300, George Mamalakis wrote:
>>  Hi all,
>> 
>> I have a FreeBSD nfsv3 server that exports a filesystem with
>> sec=krb5. Mounting the share with sec=krb5 under a fbsd client works
>> fine. I now try to mount it under linux (archlinux, upgraded today)
>> using nfs-utils. Heimdal is configured on the linux-box, kinit -k
>> linuxclient works fine. I am also able to kinit to my user
>> principals from it. When I try to mount the nvsv3 sec=krb5 share, I
>> get the following error:
>> 
>> # mount -t nfs -o sec=krb5 fbsdserver:/exports /mnt
>> 
> 
> Was there supposed to be some error output there?  Or did the mount just
> hang?
> 
>> # tail /var/log/messages
>> Sep 17 16:05:31 linuxclient rpc.statd[27683]: Version 1.2.2 starting
>> Sep 17 16:05:31 linuxclient sm-notify[27684]: Version 1.2.2 starting
>> Sep 17 16:05:31 linuxclient sm-notify[27684]: Already notifying
>> clients; Exiting!
>> Sep 17 16:05:31 linuxclient rpc.statd[27683]: Running as root.
>> chown /var/lib/nfs to choose different user
>> Sep 17 16:05:31 linuxclient sm-notify[27687]: Version 1.2.2 starting
>> Sep 17 16:05:31 linuxclient sm-notify[27687]: Already notifying
>> clients; Exiting!
>> Sep 17 16:05:53 linuxclient kernel: svc: failed to register lockdv1
>> RPC service (errno 111).
>> Sep 17 16:05:53 linuxclient kernel: lockd_up: makesock failed, error=-111
>> Sep 17 16:05:54 linuxclient kernel: svc: failed to register lockdv1
>> RPC service (errno 111).
>> Sep 17 16:05:57 linuxclient kernel: svc: failed to register lockdv1
>> RPC service (errno 111).
>> Sep 17 16:06:01 linuxclient kernel: svc: failed to register lockdv1
>> RPC service (errno 111).
> 
> 111 is ECONNREFUSED.  I'm not sure why that's failing.  (Should failure
> to register lockd fail the whole mount?

I could be wrong, but I believe that yes, it should fail the mount operation in this case, unless you specified "nolock".

> I thought it would at worst
> result in ENOLCK on lock requests?) Do you get better results if you
> mount with nolock?

-- 
chuck[dot]lever[at]oracle[dot]com




--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux