On Thu, 2012-03-22 at 16:47 -0400, J. Bruce Fields wrote:
> By the way, I finally got around to looking at the server side.
>
> We don't have any way to negotiate with the client--we don't get an
> error back if the name we return in a getattr reply isn't one the client
> likes--so I don't think I can default the new behavior to "on" without
> breaking existing setups.
>
> Other than that I think I'll just copy the client, module parameter and
> all. That allows us to do the numeric case in-kernel and avoid
> polluting our mapping cache with lots of "obvious" 123<->"123" mappings.
>
> (OK, maybe I shouldn't copy the same parameter name, though--even if it
> works it might be confusing.)
Does the idmapper do the right thing for numeric ids these days? If the
older clients are running a newer idmapper that can deal with numeric
ids, then even the legacy clients should be able to work cleanly.
Otherwise, there is also the alternative of making the whole thing a
per-client export option...
--
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�����٥
