By far most nuisance for me has been that Linux distros that ship with wheel GID different than it's <i>BSD side 0 (zero). Debian hasn't been shipping with wheel group by default, but Red Hat and many its descendants it's GID 10.<p>The macOS and BSD's don't ship with root group, Linuxen either doesn't ship with wheel group or it's GID mismatch what's on BSD side.<p>The difference will cause issues and system tools misbehaving. Bit different if NAS is </i>BSD based and using NFSv4 or newer, since user and group mapping is based names and not any more ID values they were earlier. But NFS GID mapping does not work properly whichever NFS is used, it's just different kind of misbehaving.<p>This can be fixed linux (debian etc, missing), add "wheel:x:0:" line /etc/group, right after root group. And with Red Hat based changing that GID 10 to 0.<p>Of course then /etc/idmap.conf the usual "
[Mapping]<p>Nobody-User = nobody
Nobody-Group = nogroup<p>[Translation]
Method = nsswitch
"<p>Is worth checking also.<p>The rationale adding secondary GID 0 "wheel" after first original root GID 0 is that, if you check how std <i>nix tools work, when those look up by name they will use GID what's set there, and when they look up by GID they quit looking after they find matching first value that was found.<p>Therefore above solution works both ways, and your NFS shares from </i>BSD's always shows correct value and correct group name that matches the value. I think I've learned this workaround about 30 years back now.