On Wed, 2013-08-14 at 19:24 +0000, Orion Poplawski wrote:
> Orion Poplawski <orion@...> writes:
>
> >
> > On our EL6 nfs servers we see periodic messages like:
> >
> > Aug 14 12:55:19 alexandria rpc.idmapd[19237]: nss_getpwnam: name '612' does
> > not map into domain 'cora.nwra.com'
> >
> > I imagine that this is caused by a client actually passing the uid instead
> > of the username for some reason but I have no idea how to track down which.
> > Any ideas?
Are you seeing any _actual_ application errors?
> These *appear* to be triggered by the following types of requests:
>
>
> Network File System, Ops(3): PUTFH SETATTR GETATTR
That is 100% expected behaviour if you are using AUTH_SYS on the client
(see the explanation in RFC3530bis). The default there is to use
unmapped uids and gids for backward compatibility with NFSv3, and to
ensure that the names/groups used by NFSv4 match the uids/gids used by
the AUTH_SYS authentication.
In the case where the NFSv4 server doesn't support that mode of
operation, it is expected to return NFS4ERR_BADOWNER (although Linux
clients also accept NFS4ERR_BADNAME) in which case the client will
switch to using mapped ids.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
