SMB Share Options
You can include SMB share options with the
share change, and
share create commands.
When entering options, use the following conventions:
- Separate multiple options by a comma.
- For options that can have multiple values, separate the values by a space.
CLI Example Command: Specify a write list and admin users for myshare
> share add smb myshare /stornext/snfs1/myshare write list=james doris, admin users = sysadmin
If you do not provide
public options for SMB shares, default values are set to the following:
case sensitive = auto
writable = yes
public = no
Caution: StorNext NAS manages the smb.conf and /etc/exports files on yourStorNext NAS System. Any edits made directly to either of these files will be lost when the StorNext NAS System is restarted, or when changes are made using any of the
StorNext NAS supports only a subset of SMB options, as listed in the following table:
If you need to add options to the global section of the smb.conf file, use the
share change command with the reserved share name global. In addition to any valid SMB option that can be applied to a share, the following options can be added to the global section:
map to guest
max smbd processes
winbind refresh tickets
CLI Example Command: Place the
valid users option in the global section
> share change smb global valid users = @smb-ro
Unix file systems are traditionally case sensitive, meaning that a directory can contain unique files that have the same name but different cases.
Files xyz, XYZ, and XyZ are all unique files
Windows and Mac systems traditionally support case insensitive file systems, meaning that a directory will not support unique files with the same name but different cases.
A file named XYZ is the same file as a file named xyz or as a file named XyZ.
The following sections explain how StorNext NAS uses case sensitivity with the StorNext file system.
You can configure the StorNext file system to be globally case insensitive (
caseInsensitive=true) or globally case sensitive (
In addition, you can use the
caseinsensitive=yes mount option to configure Linux clients as case insensitive. Remember that Windows and Mac clients are traditionally case insensitive but Linux clients are not. When you set the
caseinsensitive=yes mount option for a Linux client, it can access files that match on the identical spelling of a file name, but it can disregard case.
- Client X creates file abc.
- Linux client Y is configured as
caseinsensitive=yes. It requests file ABC.
- Even though ABC does not match the case of file abc, the Linux client can still access the file created by client X (abc) as ABC.
For additional information about StorNext case insensitive settings, see the StorNext 5 Man Pages Reference Guide.
By default, SMB shares are configured to be
case sensitive = auto with the global SMB share case sensitive option. With this setting, the NAS controller detects the StorNext case insensitivity settings and resets the SMB share's case sensitive option, as follows:
Global Case Insensitivity Setting
Mount Option Case Insensitivity Setting
SMB Share Case Sensitivity Reset Action
You can configure each SMB share to override the default global SMB share case sensitive option as follows:
- Configure the SMB share to access any file that matches identically on file name spelling but ignore case.
share change <share_type> (<share_name> | smb global) case sensitive = no
If a client requests file abc, the SMB share can access any file that is spelled identically, regardless of case, such as abc or ABC.
- Configure the SMB share to access the file that matches identically on both file name spelling and case.
share change <share_type> (<share_name> | smb global) case sensitive = yes
If a client requests file ABC, the SMB share can only access the file that matches exactly on spelling and case — ABC.
- If a StorNext Linux client is configured as
caseinsensitive=yes, you must configure all other clients within the StorNext cluster to use the same
In such circumstances, we recommend configuring all NAS shares to
case sensitive = auto.
- NFS shares must be served from a case sensitive file system.
valid users option, use the following syntax if the argument has a space within the name:
valid users = \"option name\"
> share change smb myshare valid users = \"@domain users\"
named streams option applies to macOS 10.11 and later.
macOS environments store metadata, including resource forks, Finder metadata, and extended attributes, for many files. In a native implementation, this metadata is referred to as Named Streams, and it is stored as a property of each file by the file system. In a non-Named Streams implementation, this metadata is stored in a secondary file — referred to as the AppleDouble file — that is paired with each primary file.
Without Named Streams, when a macOS client accesses a file system implemented with Samba, the macOS client must access both the primary file and the AppleDouble file. The macOS client must then create, maintain, and enumerate the AppleDouble file in addition to the primary file. In these types of metadata-intensive applications, Named Streams can potentially improve the performance of the application.
By enabling the
named streams option, native SMB protocol options read / write the AppleDouble files directly, saving the macOS clients from handling both the primary and AppleDouble file.
By default, the
named streams option is not enabled. You can enable the option globally for all SMB shares.
CLI Example - Enable named streams for all SMB shares
> share change smb global named streams = yes