User Guide

Option Description
● Minimum - Specifies the shortest period for which files can be locked (default value is 1 day).
● Default - Used when a file is locked and no retention period is specified.
● Maximum - Specifies the longest period for which files can be locked.
SMB Share Optionally, configure the initial SMB Share. You can add shares to the file system after the initial file
system configuration.
For details about the SMB Share options, see: Create an SMB share.
Protection
Policy
Optionally, provide a protection policy for the file system. PowerStore supports both snapshots and
replication for file storage protection.
Summary Review the summary. Go back to make necessary updates.
3. Click Create File System.
The file system is displayed in the File System list, and if you created an SMB Share, it is displayed in the SMB Share list.
File system advanced settings for SMB
You can add advanced settings to SMB-enabled file systems while creating a file system.
Table 4. File system advanced settings for SMB
Setting Description
Sync Writes Enabled When you enable the synchronous writes option for a Windows (SMB) or multiprotocol
file system, the storage system performs immediate synchronous writes for storage
operations, regardless of how the SMB protocol performs write operations. Enabling
synchronous writes operations enables you to store and access database files (for
example, MySQL) on storage system SMB shares. This option guarantees that any
write to the share is done synchronously and reduces the chances of data loss or file
corruption in various failure scenarios, for example, loss of power.
This option is disabled by default.
NOTE: The synchronous writes option can have a significant impact on
performance. It is not recommended unless you intend to use Windows file systems
to provide storage for database applications.
Oplocks Enabled (Enabled by default) Opportunistic file locks (oplocks, also known as Level 1 opslock)
enable SMB clients to buffer file data locally before sending it to a server. SMB
clients can then work with files locally and periodically communicate changes to the
storage system rather than having to communicate every operation over the network
to the storage system. This feature is enabled by default for Windows (SMB) and
multiprotocol file systems. Unless your application handles critical data or has specific
requirements that make this mode or operation unfeasible, leaving the oplocks enabled
is recommended.
The following oplocks implementations are supported:
● Level II oplocks, which informs a client that multiple clients are accessing a file, but
no client has yet modified it. A level II oplock lets the client perform read operations
and file attribute fetches by using cached or read-ahead local information. All other
file access requests must be sent to the server.
● Exclusive oplocks, which informs a client that it is the only client opening the file.
An exclusive oplock lets a client perform all file operations by using cached or
read-ahead information until it closes the file, at which time the server must be
updated with any changes that are made to the state of the file (contents and
attributes).
● Batch oplocks, which informs a client that it is the only client opening the file. A
batch oplock lets a client perform all file operations by using cached or read-ahead
information (including opens and closes). The server can keep a file opened for
a client even though the local process on the client machine has closed the file.
This mechanism curtails the amount of network traffic by letting clients skip the
extraneous close and open requests.
18 Create file systems and SMB shares