Storage object names must be unique on a server. If the server is part of a cluster, then all pools and volumes must have unique names across all servers in the cluster, whether they are in shared relationships or not.
NSS storage object names are case insensitive. Names such as AURORA, Aurora, and aurora are the same. NSS saves pool, volume, and software RAID device names in uppercase. NSS also saves labels in uppercase. For example, if you enter vol2 as the name, it is saved as VOL2.
IMPORTANT:Because Linux treats filenames as case sensitive, when using NSS volumes on Linux, make sure to mount the volume with the Long name space (ns=long) option so that file queries are case insensitive. For information, see Section 13.17, Mounting an NSS Volume on Linux to Support Case Insensitive File Names (Linux).
Device, pool, and volume names consist of at least 2 characters, but not more than 15 characters
Software RAID 0 and 5 device names consist of 2 to 128 characters.
RAID 1 device names consist of 2 to 80 characters.
Partition labels consist of 2 to 128 characters.
The encryption password for encrypted NSS volumes can be 2 to 16 standard ASCII characters, with a recommended minimum of 6.
Pathnames for files can contain up to 255 characters, including the server name, volume name, path delimiters, directory names, filename, and file extension.
Valid storage object names use the following conventions:
Can contain only valid characters:
ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_!@#$%&()
IMPORTANT:Some characters in NSS pool and volume names on OES Linux can cause problems in the /etc/fstab configuration file on Linux. Do not use ampersand ( &) and pound ( #) characters in pool and volume names.
Cannot contain spaces
Cannot begin or end with the underscore ( _)
Cannot contain multiple contiguous underscores ( __)
Cannot be one of these case-insensitive reserved names:
ALL
AUX
CLOCK
COM1
COM2
COM3
COM4
CON
LPT1
LPT2
LPT3
NETQ
NSS_ADMIN
NUL
PIPE
PRN
SYS
Because the commercial “at” character ( @) is an element of electronic mail addresses, such as code@engineer.com, it might cause confusion and possible problems in a storage object name. A Web browser or other application could mistake it for an e-mail address. We recommend that you do not use the commercial “at” character in storage object names.
The percent character ( %) might cause problems if it is passed in a format string to an application routine that uses it to delineate parameters. For example, if a volume name that contains the percent character, such as store%sales, is passed to an (s)printf routine, the (s)printf routine might look for parameters that are not there and crash. We recommend that you do not use the percent character in storage object names.