user of nfs mounted dir is 4294967294

Hi,

for some reason after sucessfully mounting a Windows Services For
Unix (no nasty comments about that pls ;-) NFS share on the linux
side as user or as root, for the mount owner the user id is -2. I'm
not using NIS on the Windows server, but manual user name mapping
(although not Simple Mapping).

I tried Google Groups and saw this problem crops up a lot, but could
not find any solution posted. Maybe someone here knows a solution?

On the Debian Sarge box the nfs mount is in /etc/fstab as:

192.168.1.108:/viaepia /opt nfs defaults,retry=1,user 0 0

Mount result is below:

jwagner@mini:/opt$ ls -al
total 2
drwxrwxrwx 2 4294967294 root 64 2007-03-17 18:36 .
drwxr-xr-x 21 root root 1024 2007-03-01 19:39 ..
drwxr-xr-x 2 jwagner jwagner 64 2007-03-17 18:36 tmp

4294967294 apparently is the "nobody" user. Any ideas why this is
not root, like the group?

And this is my mapping on the SFU server:

[Version]
3
[Domain Maps]
\\$LOCALHOST~:
[Advanced Group Mappings]
*:\\$LOCALHOST\Gäste:0:PCNFS:PCNFS:<unmapped>:-2
*:\\$LOCALHOST\Hauptbenutzer:0:PCNFS:PCNFS:jwagner :1000
*:\\$LOCALHOST\Administratoren:0:PCNFS:PCNFS:root: 0
[Advanced User Mappings]
*:<unmapped>:0:PCNFS:PCNFS:<unmapped>::-2:-2
*:\\$LOCALHOST\Administrator:0:PCNFS:PCNFS:root:** *censored***:0:0
*:\\$LOCALHOST\jwagner:0:PCNFS:PCNFS:jwagner:***ce nsored***:1000:1000
[Auth Type]
2
[Server Type]
0
[Passwd File]
jwagner:***censored***:1000:1000:jwagner::
root:***censored***:0:0:root::
[Group File]
jwagner::1000:
root::0:

(I posted the same on microsoft.public.servicesforunix.general
separately, could not crosspost to both there and this newsgroup...)

Many thanks!
- Jan

Jan Wagner wrote:
> for some reason after sucessfully mounting a Windows Services For Unix
> (no nasty comments about that pls ;-) NFS share on the linux side as
> user or as root, for the mount owner the user id is -2. I'm not using
> NIS on the Windows server, but manual user name mapping (although not
> Simple Mapping).

Almost there now. Services For Unix does not have any normal NFS
export file where you could specify no_root_squash etc.

Ended up
1) deleting the "-2" user and group from my SFU mappings, and keep
only 'root' and one user account mapping
2) setting the Administrator password to the same as the root
password on the linux box
3) editing C:\SFU\Mappings\.maphosts to allow user mapping
resolution from local and remote host (default SFU file was blank,
and no mention during install or in docs that this file has to be
edited.)
4) rebooting the SFU box

After that NFS mounting the SFU box from the linux box works, user
id of the mount is now root, same as group id, and finally no longer
4294967294, and accessing the mount as root no longer gives an I/O
error.


But the next problem: "cp -arxv / /mnt/nfsmount/" does not set
correct user and group ids to entries not owned by the 'root' or
'jwagner' account that were added to the SFU box.

So looks like SFU NFS server strips all ownership infos if unknown
local group, and replaces them with root.

$ mount
192.168.1.108:/viaepia on /opt type nfs
(rw,noexec,nosuid,nodev,retry=1,addr=192.168.1.108 )

Anyone gotten this to work with SFU?

- Jan

In comp.os.linux.networking Jan Wagner <no_spam@thanks.net>:
> Hi,

> for some reason after sucessfully mounting a Windows Services For
> Unix (no nasty comments about that pls ;-) NFS share on the linux
> side as user or as root, for the mount owner the user id is -2. I'm
> not using NIS on the Windows server, but manual user name mapping
> (although not Simple Mapping).

> I tried Google Groups and saw this problem crops up a lot, but could
> not find any solution posted. Maybe someone here knows a solution?

Do yourself a big favor and use samba/cifs, which works reliable
in 3 seconds. You can waste quite some time with SFU, but it
still remains an utter piece of crap.

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 78: Yes, yes, its called a design limitation

Michael Heiming wrote:
> Do yourself a big favor and use samba/cifs, which works reliable
> in 3 seconds. You can waste quite some time with SFU, but it
> still remains an utter piece of crap.

Well yes valid advice, SFU _is_ crap. SFU NFS runs quite stably but
pretty much none of the normal NFS features supported. But with
CIFS, the different uid/gid's don't seem to stick to the files in
CIFS either, so it's the same or actually worse than in SFU NFS.
I'll go the hard way and add the N users and groups of the linux PC
onto this XP PC.

- Jan

Jan Wagner wrote:
> Michael Heiming wrote:
>> Do yourself a big favor and use samba/cifs, which works reliable
>> in 3 seconds. You can waste quite some time with SFU, but it
>> still remains an utter piece of crap.
>
> Well yes valid advice, SFU _is_ crap. SFU NFS runs quite stably but
> pretty much none of the normal NFS features supported. But with CIFS,
> the different uid/gid's don't seem to stick to the files in CIFS either,
> so it's the same or actually worse than in SFU NFS. I'll go the hard way
> and add the N users and groups of the linux PC onto this XP PC.

There are 3rd party NFS servers for windows out there. I've not
tried any of them though.