Static Properties
Static (create-time) properties are specified at filesystem or LUN creation time, but cannot be changed after the share has been created. These properties control the on-disk data structures, and include internationalization settings, case sensitivity, and volume block size.
In the BUI, static properties can be viewed on the left side of the interface when editing a filesystem or LUN.
Table 4-2 Filesystem and LUN Static Properties
| BUI Name | CLI Name | Description |
|---|---|---|
|
Creation date |
|
Indicates the date of creation. |
|
Compression ratio |
|
Current compression ratio for the filesystem or LUN, which is a product of the compression algorithm. For more information, see Compression ratio. |
|
Case sensitivity |
|
The case sensitivity property controls whether directory lookups are case-sensitive or case-insensitive. For more information, see Case sensitivity. |
|
Reject non UTF-8 |
|
This property enforces UTF-8 encoding for all files and directories. For more information, see Reject non UTF-8. |
|
Normalization |
|
The normalization property controls 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. For more information, see Normalization. |
|
Volume block size (LUNs only) |
|
The volume block size property sets the native block size for LUNs. For more information, see Volume block size. |
|
Origin |
|
Shows the name of the snapshot from which it was cloned. For more information, see Origin. |
|
Data migration source (Filesystems only) |
|
Location of the source if the filesystem is actively shadowing an existing filesystem, either locally or over NFS. For more information, see Data Migration Source |
Compression Ratio
If compression is enabled, this property shows the compression ratio currently achieved for the share. This is expressed as a multiplier. For example, a compression of 2x means that the data is consuming half as much space as the uncompressed contents. For more information about selecting a compression algorithm, see "Data Compression" described in Inherited Properties.
Case Sensitivity
The case sensitivity property controls whether directory lookups are case-sensitive or case-insensitive. It supports the following options:
| BUI Value | CLI Value | Description |
|---|---|---|
|
Mixed |
|
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 is 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. |
|
Insensitive |
|
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. |
|
Sensitive |
|
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. |
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.0 and NFSv4.1 always use UTF-8, and SMB negotiates the appropriate encoding. This setting should normally be on, or else SMB (which must know the encoding for case sensitive comparisons, among other operations) 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, NFSv4.0 or NFSv4.1 when this property is set to off can yield undefined results if a NFSv3 client creates a file or directory that is not a valid UTF-8 encoding. This property must be set to on if the normalization property is set to anything other than none.
Normalization
The normalization property controls which 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 set to on.
| BUI Value | CLI Value | Description |
|---|---|---|
|
None |
|
No normalization is done. |
|
Form C |
|
Normalization Form Canonical Composition (NFC) - Characters are decomposed and then recomposed by canonical equivalence. |
|
Form D |
|
Normalization Form Canonical Decomposition (NFD) - Characters are decomposed by canonical equivalence. |
|
Form KC |
|
Normalization Form Compatibility Composition (NFKC) - Characters are decomposed by compatibility equivalence, then recomposed by canonical equivalence. |
|
Form KD |
|
Normalization Form Compatibility Decomposition (NFKD) - Characters are decomposed by compatibility equivalence. |
Volume Block Size
The volume block size property sets the native block size for LUNs. This can be any power of 2 from 512 bytes to 1 M, and the default is 8 K.
Note:
LUNs with a volume block size smaller than 4 K may cause performance degradation.Data Migration Source
If set, then this filesystem is actively shadowing an existing filesystem, either locally or over NFS. For more information about data migration, see Shadow Migration.