Special entries for mapping users

Special entries in the /etc/quotas file

The /etc/quotas file supports two special entries whose formats are different from the entries described in Fields of the /etc/quotas file. These special entries enable you to quickly add Windows IDs to the /etc/quotas file. If you use these entries, you can avoid typing individual Windows IDs.

These special entries are

QUOTA_TARGET_DOMAIN
QUOTA_PERFORM_USER_MAPPING

Special entry for changing UNIX names to Windows names

The QUOTA_TARGET_DOMAIN entry enables you to change UNIX names to Windows names in the Quota Target field. Use this entry if both of the following conditions apply:

The /etc/quotas file contains user quotas with UNIX names.
The quota targets you want to change have identical UNIX and Windows names. For example, a user whose UNIX name is jsmith also has a Windows name that is jsmith.

Format

The following is the format of the QUOTA_TARGET_DOMAIN entry:

QUOTA_TARGET_DOMAIN domain_name

Effect

For each user quota, Data ONTAP adds the specified domain name as a prefix to the user name. Data ONTAP stops adding the prefix when it reaches the end of the /etc/quotas file or another QUOTA_TARGET_DOMAIN entry without a domain name.

Example

The following example illustrates the use of the QUOTA_TARGET_DOMAIN entry:

QUOTA_TARGET_DOMAIN corp

roberts    user@/vol/rls         900M      30K

smith      user@/vol/rls         900M      30K

QUOTA_TARGET_DOMAIN engineering

daly       user@/vol/rls         900M      30K

thomas     user@/vol/rls         900M      30K

QUOTA_TARGET_DOMAIN

stevens    user@/vol/rls         900M      30K

Explanation of example

The string corp\ is added as a prefix to the user names of the first two entries. The string engineering\ is added as a prefix to the user names of the third and fourth entries. The last entry is unaffected by the QUOTA_TARGET_DOMAIN entry. The following entries produce the same effects:

corp\roberts       user@/vol/rls         900M      30K

corp\smith         user@/vol/rls         900M      30K

engineering\daly   user@/vol/rls         900M      30K

engineering\thomas user@/vol/rls         900M      30K

stevens            user@/vol/rls         900M      30K

Special entry for mapping names

The QUOTA_PERFORM_USER_MAPPING entry enables you to map UNIX names to Windows names or vice versa. Use this entry if both of the following conditions apply:

There is a one-to-one correspondence between UNIX names and Windows names.
You want to apply the same quota to the user whether the user uses the UNIX name or the Windows name.
Note
The QUOTA_PERFORM_USER_MAPPING entry does not work if the QUOTA_TARGET_DOMAIN entry is present.

How names are mapped

Data ONTAP consults the /etc/usermap.cfg file to map the user names.

Format

The QUOTA_PERFORM_USER_MAPPING entry has the following format:

QUOTA_PERFORM_USER_MAPPING [ on | off ]

Data ONTAP maps the user names in the Quota Target fields of all entries following the QUOTA_PERFORM_USER_MAPPING on entry. It stops mapping when it reaches the end of the /etc/quotas file or when it reaches a QUOTA_PERFORM_USER_MAPPING off entry.

Example

The following example illustrates the use of the QUOTA_PERFORM_USER_MAPPING entry:

QUOTA_PERFORM_USER_MAPPING on

roberts        user@/vol/rls         900M      30K

corp\stevens   user@/vol/rls         900M      30K

QUOTA_PERFORM_USER_MAPPING off

Explanation of example

If the /etc/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 a user with 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 a user with either user name is subject to the restriction of this quota entry.

The following entries produce the same effects:

roberts,corp\jroberts        user@/vol/rls         900M      30K

corp\stevens,cws             user@/vol/rls         900M      30K

Importance of one-to-one mapping

If the name mapping is not one-to-one, the QUOTA_PERFORM_USER_MAPPING entry produces confusing results, as illustrated in the following examples.

Example of multiple Windows names for one UNIX name

Suppose the /etc/usermap.cfg file contains the following entries:

domain1\user1 => unixuser1

domain2\user2 => unixuser1

Data ONTAP displays a warning message if the /etc/quotas file contains the following entries:

QUOTA_PERFORM_USER_MAPPING on

domain1\user1 user 1M

domain2\user2 user 1M

The /etc/quotas file effectively contains two entries for unixuser1. Therefore, the second entry is treated as a duplicate entry and is ignored.

Example of wildcard entries in usermap.cfg

Confusion can result if the following conditions exist:

The /etc/usermap.cfg file contains the following entry:
*\* *
The /etc/quotas file contains the following entries:
QUOTA_PERFORM_USER_MAPPING on unixuser2 user 1M

Problems arise because Data ONTAP tries to locate unixuser2 in one of the trusted domains. Because Data ONTAP searches domains in an unspecified order, unless the order is specified by the cifs.search_domains option, the result becomes unpredictable.

What to do after you change usermap.cfg

If you make changes to the /etc/usermap.cfg file, you must turn quotas off and then turn quotas back on for the changes to take effect. For more information about turning quotas on and off, see Turning quotas on or off.