Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Nov 2012 09:39:20 -0500
From:      Jason Keltz <jas@cse.yorku.ca>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        freebsd-net@FreeBSD.org, "Christopher D. Harrison" <harrison@biostat.wisc.edu>
Subject:   Re: kern/173479: [nfs] chown and chgrp operations fail between FreeBSD 9.1RC3 NFSv4 server and RH63 NFSv4 client
Message-ID:  <50B4D098.8030705@cse.yorku.ca>
In-Reply-To: <283018325.862373.1354024548865.JavaMail.root@erie.cs.uoguelph.ca>
References:  <283018325.862373.1354024548865.JavaMail.root@erie.cs.uoguelph.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Rick/Christopher,

Yes ...

Create a file /etc/modprobe.d, say "nfs.conf" and put in it:

options nfs nfs4_disable_idmapping=N

... and the problem will be solved.

Jason.

On 11/27/2012 08:55 AM, Rick Macklem wrote:
> Christopher D. Harrison wrote:
>> do you know what that sysctl attr is called?
>> -C
>>
> I don't recall it and it seems I've deleted his email, but Jason Keltz
> (which I've cc'd) emailed it to me and hopefully can remember it.
>
> rick
> ps: When I get it this time, I'll write it down in my note book.
>      I'm "old and old fashioned", so that's how I remember stuff;-)
>
>> On 11/26/12 21:19, Rick Macklem wrote:
>>> Christopher D. Harrison wrote:
>>>> The following reply was made to PR kern/173479; it has been noted
>>>> by
>>>> GNATS.
>>>>
>>>> From: "Christopher D. Harrison"<harrison@biostat.wisc.edu>
>>>> To: bug-followup@FreeBSD.org, jas@cse.yorku.ca
>>>> Cc:
>>>> Subject: Re: kern/173479: [nfs] chown and chgrp operations fail
>>>> between FreeBSD
>>>> 9.1RC3 NFSv4 server and RH63 NFSv4 client
>>>> Date: Mon, 26 Nov 2012 17:23:15 -0600
>>>>
>>>> The same problem also occurs in FreeBSD 9.0 release.
>>>> -C
>>>>
>>> In case you didn't see the previous discussions, this happens for
>>> Linux 3.3 or later kernels, where the default is to put the uid in
>>> a string for the owner and owner_group attributes. RFC-3530, which
>>> has not yet been replaced as the RFC for NFSv4.0 does not recommend
>>> this. A requirement for client support of this is in an internet
>>> draft called rfc3530bis, but this has not become an RFC yet.
>>>
>>> I think the Linux folks "jumped the gun" when they made this the
>>> default. You can change this using a sysctl on the server, so that
>>> it uses the<username>@<domain>  format recommended by RFC-3530 or
>>> you can upgrade to stable/9, which does have client support for
>>> the uid in a string. (The "uid in a string" was added mainly to
>>> support NFSv4 root mounts for diskless clients.)
>>>
>>> This PR will be closed when I get home next week and can do so.
>>>
>>> rick
>>>
>>>> _______________________________________________
>>>> freebsd-net@freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>>>> To unsubscribe, send any mail to
>>>> "freebsd-net-unsubscribe@freebsd.org"
>> _______________________________________________
>> freebsd-net@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B4D098.8030705>