Red Hat Bugzilla – Bug 1359407
[RGW:NFS]:- Strange uid:gid for the buckets (directories)created through nfs mount
Last modified: 2017-07-30 11:53:30 EDT
Description of problem: If we create buckets (directories) from nfs mount then uid:gid will be strange and doesn't belongs to any of the user from both client and ganesh node. Version-Release number of selected component (if applicable): ceph-radosgw-10.2.2-26.el7cp.x86_64 nfs-ganesha-rgw-2.3.2-2.el7cp.x86_64 How reproducible: always Steps to Reproduce: 1. setup nfs-rgw and mount it 2. create a directory and observe uid:gid [root@magna110 mnt]# ll total 0 drwxr-xr-x. 3 4294967294 4294967294 0 Jul 23 19:51 another drwxrwxrwx. 3 root root 0 Jan 1 1970 another-missed-hellonew-another-newad-bucket-creation drwxrwxrwx. 3 root root 0 Jan 1 1970 hellonew-another-newad-bucket-creation drwxrwxrwx. 3 root root 0 Jan 1 1970 missed-hellonew-another-newad-bucket-creation drwxrwxrwx. 3 4294967294 4294967294 0 Jul 23 13:11 nfsbucket observer the uid:gid for the "nfsbucket" and "another" directories.
For 2.0, this is Not-A-Bug. The uid (gid) 4294967294 is the default nobody (nogroup) id of nfs-ganesha. The root cause of the inconsistency is nfs-ganesha not correctly configured for proper id mapping. The current writeup for the RGW-NFS feature does not specify how id mapping should be performed. We have added to nfs-ganesha a new, simplified id mapping options ("only_numeric_owners") which will trust client-supplied ids and save/return them without modification. This will allow sites (and QE) to validate ownership operations without requiring a shared id mapping domain. While I feel this is not a bug, I'm moving this to 2.1 for verification with the updated nfs-ganesha 2.4 which has the new id mapping feature.