Adam, While what you've described is correct, there is one inherent misconception.  Yes an auto-generated UID/GID will be created for a user upon first connection if they have no matching account in LDAP/NIS/File Provider, etc.  However if you were to add an LDAP account for them later, even though the output of isi auth mapping dump | grep will show you the auto-created mapping, that is the last resort we use.  So if a valid UID/GID suddenly becomes available, it will now be used, and the auto-created one is merely an artifact that does not matter.  On a VNX this is a bigger problem, because the on-disk identity is always Unix, since the UXFS filesystem is based on EXT3, it must have a valid UID and GID to write anything to disk.  But on Isilon, if a user is SMB-only for 5 years, then all of a sudden gets an LDAP account, the data they've been writing for those 5 years will all have SID as the on-disk Identity, so there is no need to re-permission the data. You can verify this with a sample user created in AD without a match, write some data, look at the output of isi auth mapping token domain\\username, find the 2 mapping entries for that SID in 'isi auth mapping dump'.  Then create an LDAP account for that user.  Now re-run the isi auth mapping token domain\\username.  See if the UID and GID change.  They should assuming the user mapping rules are setup properly.  Now run an ls -ln /ifs/
   .  See if the UID and GID show are in the 1,000,000-2,000,000 range, or are what should be coming from LDAP.  
  So in that way the platform can be extremely flexible for this type of workflow.  ~Chris Klosterman Senior Solution Architect EMC Isilon Offer & Enablement Team chris.klosterman[NAME].com twitter: [NAME]
Hi Fellow Isiloners,  Need urgent assistance! I have copied over Mixed security shares from Netapp to Isilon. These directories are now Shared as SMB as well Exported to Linux client.  Client creates a file on the share and accesses it over the linux system but it's noticed that his GID/UID are not maintained. Seems it's taking isilon default UID and that's a problem . Can anyone assist how I can re-mediate this ?  Utkarsh
Multi-protocol issue UID/GID not matching