Administrator Guide

Accessing an SMB Share Using UNIX or Linux
Mount the SMB share from a UNIX or Linux operating system using one of the following commands:
# mount -t smbfs -o user_name=user_name,password=password//client_vip_or_name/
smb_share_name/local_folder
# smbmount //client_vip_or_name/smb_share_name/local_folder -o user_name=user_name
Managing NFS Exports
Network File System (NFS) exports provide an effective way of sharing files across a UNIX or Linux network with authorized
clients. After creating NFS exports, NFS clients then need to mount each NFS export. The FluidFS cluster fully supports NFS
protocol version 3 and all requirements of NFS protocol versions 4.0 and 4.1.
● Supported NFSv4 features:
○ File and byte-range locking
NOTE: Starting with FluidFS v6, if the multitenancy feature is enabled, NAS administrators can configure NFSv4 to
switch from mandatory to advisory byte-range locks at the tenant level using the CLI.
○ Kerberos v5 security using an AD server
○ AUTH_SYS legacy weak authentication
○ UID translation using an LDAP server (UNIX or AD) or a NIS server
○ UTF-8 file and directory names
● Unsupported NFSv4 features:
○ Delegation of file locks to clients
○ Full interoperability between NFSv3 and NFSv4 (for example, conflict resolution for locks from clients using different
protocols)
○ Antivirus scanning and result caching
○ LIPKEY and SPKM-3 security (not mandatory in NFSv4.1)
○ Kerberos UNIX server
NFS v4 Implementation
Before implementing NFSv4, note the following, and refer to the respective documentation for your NFSv4 clients:
● User and Group identification — NFSv4 users and groups are identified by a <name>@<domain> string (rather than the
traditional UID/GID numbers). The NFSv4 server (FluidFS) and clients must be configured to use the same external Network
Information Service (NIS) or LDAP domain, which ensures consistent <UID/GID>-<name> mapping of identities. If the string
does not map to a domain object, it defaults to the nobody identity.
● Protection mode— Configure the NAS volume with UNIX security style to allow NFSv4 ACLs. NFSv4 ACLs are supported,
but POSIX ACLs are not.
● Interoperability —
○ You can modify permissions or ownership to NFSv4 ACL on UNIX volumes. NFSv4 clients can transparently access
UNIX/POSIX or NTFS protected files. The accessing identity is translated and checked against the UNIX/POSIX or NTFS
ACL metadata (permissions and ownership), to verify access authorization.
○ NFSv4 ACL-protected objects can analogously be accessed by NFSv3 and SMB clients.
● Single port configuration — NFSv4 communicates over TCP port 2049 only.
For detailed information about the Network File System (NFS) version 4 protocol, see RFC 7530.
418
FluidFS Administration