NAS Share Tips and FAQs
Mac SMB clients may not be able to create hard links even though Unix extensions have been enabled on the SMB share.
You can create hard links on the Samba server to use from the Mac SMB client.
If you use AD authentication with the RFC2307 ID map option and issue the
share create command, the system will return the following error:
user 'administrator' not found (E-5060)
When issued, the
share create command assigns default ownership settings. If you have configured your StorNext NAS System to use AD authentication with the RFC2307 ID map option, the share directories will have the UID and GID assigned by the RFC2307 ID map option. However, Samba does not recognize the UID, and rejects the
share create command as a security violation.
You can do one of the following to resolve the issue.
You can add shares to the directory by issuing the
share add command. Keep in mind that you will need to create the share directory before issuing this command.
See Create Shares.
You can re-issue the
auth config ads command with one of the following ID map options:
The Relative Identifier (RID) ID map option converts a Security Identifier (SID) to an RID, using an algorithm that allows all Quantum appliances to see the same UID.
The Trivial Database (TDB) ID map option tells Samba to generate UIDs and GIDs locally on demand.
If you share volumes that under Storage Manager Control, you could experience the following issues.
Apple SMB clients do not recognize offline (truncated) files. If you use Finder along with Show icon preview to locate a file, the process will attempt to read each file — including offline files — in the folder to generate a preview. This process causes the SMB connection to hang while trying to retrieve offline files.
To avoid this issue, we recommend disabling Show icon preview. We also recommend against using Finder so that a file retrieve is not generated.
Apple SMB clients save file attributes in the Apple Double File. Every time that Finder is used or that the
ls -l command issued, the Apple SMB client reads the saved file attributes. Depending on the Archive destination, the file retrieves can cause the SMB connection to hang if offline (truncated) files are included in the Apple Double File.
To avoid this issue, ensure that the Apple Double File is excluded from the truncation policy. Perform this exclusion from the primary node by populating the
/usr/adic/TSM/config/excludes.truncate file with the following line:
Note: If the
/usr/adic/TSM/config/excludes.truncate file does not exist, you need to create it on the primary node.
If an NFS client tries to access an offline file under Storage Manager Control, the process could hang until the file becomes available.
To avoid this issue, use the
dmnfsthreads=<value> mount option.
For more information, see StorNext 5 Man Pages Reference Guide.
NFS clients may be unable to mount shares if one of the following two scenarios is at play.
NFS clients cannot distinguish between two NFS shares that are exported from the same underlying StorNext file system.
By default, the Linux NFS server uses the underlying StorNext file system's UUID to identify an exported share. However, shares exported from the same StorNext file system have the same UUID, and therefore, NFS clients cannot differentiate between them. Without being able to differentiate between shares, the NFS client cannot mount a share.
To resolve this issue, you can assign a unique file system ID to each share.
From the NAS console command line, issue the following command to assign a file system ID to each NFS share exported from the StorNext file system:
share change nfs <share_name> fsid=<unique_file_system_ID>
See Modify Shares.
If you attempt to mount an NFS share on an OS X client, you may receive an
Operation is not permitted … error message.
This error can occur when OS X clients cannot mount NFS shares that are exported with secure options.
Perform one of the following steps to resolve this issue:
resvportoption when mounting the NFS share.
CLI Example Command: Issued from OS X terminal
$ mount_nfs –o resvport server:/path directory
- Include the
insecureoption when adding or changing options for an NFS share
> share add nfs myshare /stornext/snfs/myshare ro,insecure
If you run the
df command from an OS X system, the NAS controller could report invalid or misleading information about your NAS shares.
If you attempt to share a directory over both SMB and NFS protocols, you risk file corruption, stale file locks, and other file access issues in the share. Because of these incompatibility issues, we strongly recommend against sharing a directory over both SMB and NFS protocols.
For additional information, see https://access.redhat.com/solutions/1983.