Shares are file systems and LUNs that are exported over supported data protocols to compute nodes. File systems export a file-based hierarchy and can be accessed over NFS over IPoIB in Exalogic machines.
To create a custom share, such as domain_home
under the Dept_1
project, do the following:
The shares page is displayed.
Dept_1
.domain_home
.Table 8-3 File System Access Types and Permissions
Access Type | Description | Permissions to Grant |
---|---|---|
User |
User that is the current owner of the directory. |
The following permissions can be granted:
|
Group |
Group that is the current group of the directory. |
|
Other |
All other accesses. |
You can use this feature to control access to the file system, based on the access types (users and groups) in Dept_1
.
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
.
Note:
This option is selected only when you are creating the file system.
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.
Table 8-5 Normalization Settings
BUI 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. |
Note:
This option is selected only when you are creating the file system.