Table of Contents
Advertisement
Cannot conflict with another share
■
Cannot conflict with another share on cluster peer to allow for proper failover
■
When inheriting the mountpoint property, the current dataset name is appended to the project's
mountpoint setting, joined with a slash ('/'). For example, if the "home" project has the
mountpoint setting /export/home, then "home/bob" would inherit the mountpoint /export/
home/bob.
SMB shares are exported via their resource name, and the mountpoint is not visible over
the protocol. However, even SMB-only shares must have a valid unique mountpoint on the
appliance.
Mountpoints can be nested underneath other shares, though this has some limitations. For more
information, see
"Working with Filesystem Namespace" on page
Read only
The read-only property controls whether the filesystem contents are read only. This property is
only valid for filesystems.
The contents of a read-only filesystem cannot be modified, regardless of any protocol settings.
This setting does not affect the ability to rename, destroy, or change properties of the filesystem.
In addition, when a filesystem is read only, access control properties cannot be altered, because
they require modifying the attributes of the root directory of the filesystem.
Update access time on read
The update access time on read property controls whether the access time for files is updated on
read. This property is only valid for filesystems.
POSIX standards require that the access time for a file properly reflect the last time it was read.
This requires issuing writes to the underlying filesystem even for a mostly read-only workload.
For working sets consisting primarily of reads over a large number of files, turning off this
property may yield performance improvements at the expense of standards conformance. These
updates happen asynchronously and are grouped together, so its effect should not be visible
except under heavy load.
Non-blocking mandatory locking
The non-blocking mandatory locking property controls whether SMB locking semantics are
enforced over POSIX semantics. This property is only valid for filesystems.
Project and Share Properties
399.
Shares and Projects
365
Advertisement
Table of Contents
