(In reply to comment #6)
> I don't see the issue between 2 Fedora 18 machines.
I wanted to investigate the issue between two Fedora 18 machines.
Unfortunately I couldn't find a way to activate the uid mapping mechanism.
Everything I tried had simply results compatible with nfs version 3.
My test case was:
1. create a user "testnfs" on both the server and client with different
UIDs
2. create a file on the server with (local) ownership by testnfs
3. nfs-mount the directory on the client machine and investigate the ownership
of the file by the (local on the client) testnfs user.
I espect ownership (e.g. uid is remapped), which is *not* the case.
---
The same experiment carried on a Fedora 16 server, kernel 3.3.5-2.fc16.i686.PAE
nfs-utils-1.2.5-5.fc16.i686, on the contrary gave the expected uid remapping.
---
Not that I actually *need* remapping (on the contrary!), this is just to
understand whether the problem is transient, and solved for the future or not.
(In reply to comment #6)
> I don't see the issue between 2 Fedora 18 machines.
I wanted to investigate the issue between two Fedora 18 machines.
Unfortunately I couldn't find a way to activate the uid mapping mechanism.
Everything I tried had simply results compatible with nfs version 3.
My test case was:
1. create a user "testnfs" on both the server and client with different
UIDs
2. create a file on the server with (local) ownership by testnfs
3. nfs-mount the directory on the client machine and investigate the ownership
of the file by the (local on the client) testnfs user.
I espect ownership (e.g. uid is remapped), which is *not* the case.
---
The same experiment carried on a Fedora 16 server, kernel 3.3.5-2. fc16.i686. PAE 1.2.5-5. fc16.i686, on the contrary gave the expected uid remapping.
nfs-utils-
---
Not that I actually *need* remapping (on the contrary!), this is just to
understand whether the problem is transient, and solved for the future or not.