Table of Contents
Advertisement
Project and Share Properties
BUI Value
Mixed
Insensitive
Sensitive
Reject non UTF-8
This property enforces UTF-8 encoding for all files and directories. When set, attempts to create
a file or directory with an invalid UTF-8 encoding will fail. This only affects NFSv3, where the
encoding is not defined by the standard. NFSv4 always uses UTF-8, and SMB negotiates the
appropriate encoding. This setting should normally be "on", or else SMB (which must know
the encoding in order to do case sensitive comparisons, among other things) will be unable to
decode filenames that are created with and invalid UTF-8 encoding. This setting should only
be set to "off" in pre-existing NFSv3 deployments where clients are configured to use different
encodings. Enabling SMB or NFSv4 when this property is set to "off" can yield undefined
374
Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016
CLI Value
mixed
insensitive
sensitive
Description
Case sensitivity depends on the
protocol being used. For NFS,
FTP, and HTTP, lookups are case-
sensitive. For SMB, lookups are
case-insensitive. This is default,
and prioritizes conformance of the
various protocols over cross-protocol
consistency. When using this mode,
it's possible to create files that are
distinct over case-sensitive protocols,
but clash when accessed over SMB.
In this situation, the SMB server will
create a "mangled" version of the
conflicts that uniquely identify the
filename.
All lookups are case-insensitive,
even over protocols (such as
NFS) that are traditionally case-
sensitive. This can cause confusion
for clients of these protocols, but
prevents clients from creating name
conflicts that would cause mangled
names to be used over SMB. This
setting should only be used where
SMB is the primary protocol and
alternative protocols are considered
second-class, where conformance to
expected standards is not an issue.
All lookups are case-sensitive,
even over SMB where lookups are
traditionally case-insensitive. In
general, this setting should not be
used because the SMB server can
deal with name conflicts via mangled
names, and may cause Windows
applications to behave strangely.
Advertisement
Table of Contents
