Case Sensitivity Values - Oracle Exalogic Elastic Cloud Owner's Manual

Table of Contents

Advertisement

Note:
The mount point must be under /export. The mount point for one share
cannot conflict with another share. In addition, it cannot conflict with another
share on cluster peer to allow for proper failover.
When inheriting the mountpoint property, the current dataset name is
appended to the project's mountpoint setting, joined with a slash ('/'). For
example, if the domain_home project has the mountpoint setting /export/
domain_home, then domain_home/config inherits the mountpoint /
export/domain_home/config.
To enforce UTF-8 encoding for all files and directories in the file system, select the
8.
Reject non UTF-8 option. When set, any attempts to create a file or directory with
an invalid UTF-8 encoding will fail.
Note:
This option is selected only when you are creating the file system.
From the Case sensitivity pull-down menu, select Mixed, Insensitive, or Sensitive
9.
to control whether directory lookups are case-sensitive or case-insensitive.
Table 8-4

Case Sensitivity Values

BUI Value
Description
Mixed
Case sensitivity depends on the protocol being used. For NFS, FTP, and
HTTP, lookups are case-sensitive. This is default, and prioritizes
conformance of the various protocols over cross-protocol consistency.
Insensitive
All lookups are case-insensitive, even over protocols (such as NFS) that
are traditionally case-sensitive. This setting should only be used where
CIFS is the primary protocol and alternative protocols are considered
second-class, where conformance to expected standards is not an issue.
Sensitive
All lookups are case-sensitive. In general, do not use this setting.
Note:
This option is selected only when you are creating the file system.
From the Normalization pull-down menu, select None, Form C, Form D, Form
10.
KC, or Form KD to control what unicode normalization, if any, is performed on
filesystems and directories. Unicode supports the ability to have the same logical
name represented by different encodings. Without normalization, the on-disk name
stored will be different, and lookups using one of the alternative forms will fail
depending on how the file was created and how it is accessed. If this property is set
to anything other than None (the default), the Reject non UTF-8 property must
also be selected.
Create Custom Shares
Configure the Storage Appliance 8-19

Advertisement

Table of Contents
loading

Table of Contents