Are quotas listed correctly when you use an explicit "--zone ..."  specification with "isi quota ..." ?
Help me understand why I'm seeing this, I assume I'm doing something wrong because this doesn't make sense.  Up until now, I've only had AD and NIS as authentication sources (but I'm still not using AD, so basically just using NIS), and when I added quotas to user's home folders, the owner matches up to what NIS sees.  I have an access zone for NIS and this content.  To date, everything seems normal... quotas are assigned to correct owners based on what NIS has.  I just added an OpenLDAP authentication source which will have about 50 or so users eventually specific to our high performance computing cluster.  This must remain separate so I also created another access zone specific to OpenLDAP and this content.  However, my System access zone can see both NIS and OpenLDAP now.  When I went to create user quotas specific for these users, there obviously is a UidNumber conflict between NIS and OpenLDAP because it's reporting the "linked user" of those home folders being from the NIS source.  When I purposely created a user in OpenLDAP with a UidNumber of 50,000 it reports the correct OpenLDAP user.  Can anyone explain what I'm doing wrong and how I should be doing this?  I'm keeping the authentication sources separated by access zones for the content, but what's up with the quotas?  Obviously I could just pick high UidNumbers for my OpenLDAP users, what would happen if I had two sources (say two distinct LDAP servers) with thousands of established users with overlapping UidNumbers and needed quotas for the users from each source?  Thanks for the help.
Authentication Source and Quotas