For all clients types

Content Software for File CLI Reference

Version
4.2.x
Audience
anonymous
Part Number
MK-HCSF001-03
Option Value Description Default
readcache None Set mode to read cache No
writecache None Set mode to write cache Yes
dentry_max_age_positive Number in milliseconds After the defined time period, every metadata cached entry is refreshed from the system, allowing the host to take into account metadata changes performed by other hosts. 1000
dentry_max_age_negative Number in milliseconds Each time a file or directory lookup fails, an entry specifying that the file or directory does not exist is created in the local dentry cache. This entry is refreshed after the defined time, allowing the host to use files or directories created by other hosts. 0
ro None Mount filesystem as read-only No
rw None Mount filesystem as read-write Yes
inode_bits 32, 64 or auto Size of the inode in bits, which may be required for 32-bit applications. Auto
verbose None Write debug logs to the console No
quiet None Don't show any logs to console No
acl None Can be defined per mount. Setting POSIX ACLs can change the effective group permissions (via the mask permissions). When ACLs defined but the mount has no ACL, the effective group permissions are granted.) No
obs_direct None See Object-store Direct Mount section No
noatime None Do not update inode access times No
strictatime None Always update inode access times No
relatime None Update inode access times only on modification or change, or if inode has been accessed and relatime_threshold has passed. Yes
relatime_threshold Number in seconds How much time (in seconds) to wait since an inode has been accessed (not modified) before updating the access time.

0 means to never update the access time on access only. This option is relevant only if relatime is on.

0 (infinite)
nosuid None Do not take suid/sgid bits into effect. No
nodev None Do not interpret character or block special devices. No
noexec None Do not allow direct execution of any binaries. No
file_create_mask Numeric (octal) notation of POSIX permissions Newly created file permissions are masked with the creation mask. For example, if a user creates a file with permissions=777 but the file_create_mask is 770, the file will be created with 770 permissions. First, the umask is taken into account, followed by the file_create_mask and then the force_file_mode. 0777
directory_create_mask Numeric (octal) notation of POSIX permissions Newly created directory permissions are masked with the creation mask. For example, if a user creates a directory with permissions=777 but the directory_create_mask is 770, the directory will be created with 770 permissions. First, the umask is taken into account, followed by the directory_create_mask and then the force_directory_mode. 0777
force_file_mode Numeric (octal) notation of POSIX permissions Newly created file permissions are logically OR'ed with the mode. For example, if a user creates a file with permissions 770 but the force_file_mode is 775, the resulting file will be created with mode 775. First, the umask is taken into account, followed by the file_create_mask and then the force_file_mode. 0
force_directory_mode Numeric (octal) notation of POSIX permissions Newly created directory permissions are logically OR'ed with the mode. For example, if a user creates a directory with permissions 770 but the force_directory_mode is 775, the resulting directory will be created with mode 775. First, the umask is taken into account, followed by the directory_create_mask and then the force_directory_mode. 0
sync_on_close This option ensures that all data for a file is written to the server when the file is closed. This means that changes made to the file by the client are immediately written to the server's disk upon close, which can provide greater data consistency and reliability. It simulates the open-to-close semantics of NFS when working with writecache mount mode and directory quotas. Enabling this option is essential when applications expect returned write errors at syscall close if the quota is exceeded. No Yes
nosync_on_close This option disables the sync_on_close behavior of file writes. When nosync_on_close is enabled, the client does not wait for the server to confirm that all file data has been written to disk before closing the file. This means that any changes made to the file by the client may not be immediately written to the server's disk when the file is closed. Instead, the changes are buffered in memory and written to disk asynchronously later. No Yes