Table of ContentsView in Frames

How you map names using the QUOTA_PERFORM_USER_MAPPING directive

If you have configured the system's /etc/usermap.cfg file with a one-to-one correspondence between UNIX names and Windows names, the QUOTA_PERFORM_USER_MAPPING directive in the quotas file automatically links the names. You do not have to add a separate entry for each user.

When you use this directive, Data ONTAP consults the usermap.cfg file to map the user names. When a UNIX and Windows name are mapped together, they are treated as the same person for determining quota usage.

For more information about the usermap.cfg file, see the Data ONTAP File Access and Protocols Management Guide for 7-Mode.

Note: If you use the user mapping feature, make sure that CIFS is either completely configured or not licensed. Leaving CIFS installed but not configured while using user mapping could impact storage system performance.
Note: This directive requires a one-to-one correspondence between Windows names and UNIX names. If a name maps to more than one name in the usermap.cfg file, there are duplicate entries in the quotas file and you might see unpredictable results.
Note: If you are using this directive, when you make changes to the usermap.cfg file, you must turn quotas off and back on before your changes will take effect.

Example

The following example illustrates the use of the QUOTA_PERFORM_USER_MAPPING directive:
QUOTA_PERFORM_USER_MAPPING ON
roberts        user@/vol/vol2         900M      30K 
corp\stevens   user@/vol/vol2         900M      30K 
QUOTA_PERFORM_USER_MAPPING OFF

If the usermap.cfg file maps roberts to corp\jroberts, the first quota entry applies to the user whose UNIX name is roberts and whose Windows name is corp\jroberts. A file owned by either user name is subject to the restriction of this quota entry.

If the usermap.cfg file maps corp\stevens to cws, the second quota entry applies to the user whose Windows name is corp\stevens and whose UNIX name is cws. A file owned by either user name is subject to the restriction of this quota entry.

The effect of this example could also be achieved with multiple user names in a single quotas file entry, as in the following example:
roberts,corp\jroberts        user@/vol/vol2         900M      30K 
corp\stevens,cws             user@/vol/vol2         900M      30K