Oracle ZFS Storage Appliance: NFSv4 Client - New User sees created files owned by Different User

Asset ID:	1-72-2099401.1
Update Date:	2017-04-25
Keywords:

Solution Type Problem Resolution Sure

Solution 2099401.1 : Oracle ZFS Storage Appliance: NFSv4 Client - New User sees created files owned by Different User

Applies to:

Oracle ZFS Storage ZS5-4 - Version All Versions and later
Oracle ZFS Storage ZS5-2 - Version All Versions and later
Oracle ZFS Storage ZS4-4 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS4-4 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

User is having issues with permissions on the ZS3-3 NFS shares. Here are some background details.

The user's account was initially created in LDAP as jonathan.doe and shortly after he asked for the username to be changes to jon.doe.

The New account was created for jon.doe with a unique UID.

We have a Linux client which is mounting a share from the ZFSSA using NFSv4 . The ZFSSA uses the same domain and name database as the client.

If we login as the new user (jon.doe) ID reflects the new UID.

If I now create a fille on the share as this new user , and then check ownership, it is owned by the original username.

Then if I chown to jon.doe it reports no errors, but when we check file ownership it is still owned by jonathan.doe.

Checking with "ls -ln" also shows the incorrect UID.

Summary : We can create files as the new owner, however when we check ownership the file is being seen as owned by the old username.

Cause

This issue is only seen on the NFSv4 mounted share.

On the local Linux filesystem the user ownership worked correctly as expected.

Also verified on the ZFS-SA itself that the File ownership was working correctly. The issue is with NFSv4.

Unmounted the share and remounted as NFSv3. The file ownership worked correctly as expected.

The main difference is that NFSv3 uses UID/GID and NFSv4 uses domain naming.

To perform this NFSv4 uses the NFSmapid process .

We can see the idmapcache from the support bundle is missing an entry for the new name:

% grep -i smith idmapcache.out
idmapcache.out:winuser:jonathan.doe@oracle.local == gid:2184657487
idmapcache.out:winuser:jonathan.doe@oracle.local == uid:2184657388
idmapcache.out:winuser:jon.doe@oracle.local == gid:2184657392

Solution

At the current time. there is no way to flush the nfsmapid cache - other than restarting the NFS service.

Either using Configuration > Services > NFS in the ZFSSA BUI , or by rebooting.

References

<BUG:21976462> - REQUIRE METHOD TO REFRESH NFS MAPID CACHE WITHOUT RESTARTING NFS

Attachments

This solution has no attachment