Project and Share Properties
inherited like most other standard properties. The values are never consumed by the software
in any way, and exist solely for end-user consumption. The property schema is global to the
system, across all pools, and is synchronized between cluster peers.
Related Topics
■
“Space Management for Shares” on page 396
■
“Project and Share Properties” on page 363
■
“Snapshots and Clones” on page 437
Project and Share Properties
All projects and shares have a number of associated properties which can be set using the BUI
or CLI. For a list of property names and descriptions, click on one of these links:
■
“Project Properties” on page 376
■
“Filesystem Properties” on page 382
■
“LUN Properties” on page 390
Project and share properties can be one of the following types:
TABLE 102
Project and Share Property Types
Property Type Description
Inherited Inherited properites, the most common property type,
represent most of the configurable project and share
properties. Shares that are part of a project can either
have local settings for properties, or they can inherit
their settings from the parent project. By default, shares
inherit all properties from the project. If a property is
changed on a project, all shares that inherit that property
are updated to reflect the new value. When inherited, all
properties have the same value as the parent project, with
the exception of the mountpoint and SMB properties.
When inherited, these properties concatenate the project
setting with their own share name.
Read only Read-only properties represent statistics about the project
and share and cannot be changed. The most common
properties of this type are space usage statistics.
Space management Space management properties (quota and reservation)
apply to both shares and projects, but are not inherited.
A project with a quota of 100G will be enforced across
all shares, but each individual share will have no quota
unless explicitly set.
Shares and Projects 363
To Next Page
Loading...
Need help?
General