Summary: NFS mount problem

Dear manager,

thanks to

"Charles Morris" <cmorris@cs.odu.edu>
Lawrence Sorrillo <sorrillo@jlab.org>
Roderick Grau" <RGrau@uamail.albany.edu>
Stefan Varga <Stefan_Varga@tempest.sk>
Aleks Feltin <aleksf@scms.fi>

> I have nfs-exported /home with zfs on server A as follows
>
> 	zfs create tank/home
> 	zfs set mountpoint=/home tank/home
> 	zfs set sharenfs=rw tank/home
> 	zfs share tank/home
>
> and mount that on client B as follows
>
> 	svcadm disable autofs
> 	mkdir /home
> 	mount -F nfs 192.168.1.1:/home /home
>
> I have copied /etc/passwd, /etc/group and /etc/shadow from server A to 
> client B. I can log into client B as ahoesch and also list my files 
> but when doing "ls -l" I get
>
> ...
> -rw-------   1 nobody   nobody       136 Aug 18  2004 local.cshrc
> -rw-------   1 nobody   nobody       157 Aug 18  2004 local.login
> -rw-------   1 nobody   nobody       174 Aug 18  2004 local.profile
> drwx------   2 nobody   nobody         7 May  9 15:57 mail
> -rw-r--r--   1 nobody   nobody   2073088 May  8 18:48 maritim.tar
> -rwx------   1 nobody   nobody      2025 Nov 19  2004 
> merkurSync.command
> ...
>
> Why does client B think these files owned by nobody? When I do the 
> same ls -l on server A I get
>
> ...
> -rw-------   1 ahoesch  other        136 Aug 18  2004 local.cshrc
> -rw-------   1 ahoesch  other        157 Aug 18  2004 local.login
> -rw-------   1 ahoesch  other        174 Aug 18  2004 local.profile
> drwx------   2 ahoesch  other          7 May  9 16:22 mail
> -rw-r--r--   1 ahoesch  other    2073088 May  8 18:48 maritim.tar
> -rwx------   1 ahoesch  other       2025 Nov 19  2004 
> merkurSync.command
> ...
>
> Since both machines have the same accounts I am wondering what that 
> means. I read "man mount" but got no hint. postfix is complaining that 
> /home/ahoesch/.forward has a bad userId (--> nobody) on client B. 
> That's why I started to look into this. What am I missing?

The problem was caused by different values of NFSMAPID_DOMAIN (cat 
/var/run/nfs4_domain). Modifying the contents of /var/run/nfs4_domain 
has no effect. The value is modified during reboot. I therefore made 
sure /etc/resolv.conf has the same domain entry on both machines. After 
a reboot of the client, the problem was gone. Aleks Feltin 
<aleksf@scms.fi> pointed me to  /etc/default/nfs which can have an 
entry for NFSMAPID_DOMAIN. If one really needs different domains in 
/etc/resolv.conf one can probably fix the problem as well by defining 
NFSMAPID_DOMAIN in this file. However, I can live with identical 
resolv.conf domains so I haven't tried that out yet.

Thanks a lot for your kind help!!!

Regards,

   Andreas
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers