Nicolas Williams wrote: > On Mon, Aug 04, 2008 at 10:37:04AM -0500, Paul Fisher wrote: > >> I'm trying to use NFSv4 mounts and idmap to deal with differences in the >> uid/gid values between the server and clients. It is my understanding >> that NFSv4/idmap will map names->ids, and not use the id values >> directly. Is this correct? >> > > Sortof. > > NFSv4 uses names on the wire. > > The Solaris NFSv4 stack supports only one Unix domain, plus it supports > all of an Active Directory (Windows) forest. > > What you're trying to do, evidently, is use multiple Unix domains. We > don't support that yet. > Actually no, only one nfs domain called "localnet" which is set on both the client and the server. What is different is that the client and server have a different idea of the actual uid/gid values that are used for the names (all in the local /etc files on each system).
If NFSv4 idmap'ing uses names, but the uid/gid values on both sides need to match, what is the purpose of this translation layer? What am I missing here? >> - Domain = localnet (etch-01 -> /etc/idmapd.conf >> > > There is no idmapd.conf on Solaris. > Um, did you missed that the client was Debian Etch Linux? Linux does in fact have this file, which is where the idmap domain name is set. If you look at the ls -l /export/home (on the os system), and ls -l /home (on the etch-01 system) in the original post, you can see that the name->id mapping seems to work for directory listings, but something else is going on when accessing the contents. -- paul
