How to Apply Deferred Updates (CLI)
In order to use this new mode, the storage pool must be upgraded. If you choose not to upgrade
the pool and attempt to use this new property, you will get an error indicating that the storage
pool needs to be upgraded first. There is no other implication of applying this update, and it
can be ignored if there is no need to use this new setting. Applying this update is equivalent to
upgrading the on-disk ZFS pool to version 17.
Support for COMSTAR Deferred Update
The COMSTAR framework relies on a ZFS pool upgrade for complete support of persistent
group reservations (PGRs). Before this upgrade has been applied, the number of reservations
stored with each LUN is severely limited, and may even be zero.
Applying this update is equivalent to upgrading the on-disk ZFS pool to version 16.
Support for User Quotas Deferred Update
With the 2009.Q3 software release, the system now supports user and group quotas on a per-
share basis. In order to make use of this feature, a deferred update must be applied to upgrade
all shares in the system to support this feature. Applying this deferred update also allows the
current usage (user or group) to be queried on a per-filesystem or per-project basis. To quote the
product documentation:
Quotas can be set on a user or group at the filesystem level. These enforce physical data usage
based on the POSIX or Windows identity of the owner or group of the file or directory. There
are some significant differences between user and group quotas and filesystem and project data
quotas.
Be sure to completely read “Space Management for Shares” in Oracle ZFS Storage Appliance
Administration Guide, Release 2013.1.5.0 before attempting to use user or group quotas.
This update is applied in the background, and takes time proportional to the number of shares
and amount of data on the system. Until this deferred update is finished, attempts to apply user
quotas produce an error indicating that the update is still in progress.
Support for Passthrough x Deferred Update
For filesystems, ACLs are inherited according to the "aclinherit" property on the filesystem (or
inherited from the project). Previous versions of software allowed four options for this setting:
"discard", "noallow", "restricted", and "passthrough". The 2009.Q2.0.0 release introduces
a new option, "passthrough-x", with slightly different semantics as described in the product
documentation:
306 Oracle ZFS Storage Appliance Customer Service Manual • February 2016
To Next Page
Loading...
Need help?
General