Editor
19
edits
Line 47: | Line 47: | ||
We worked on supporting this using the ASIZE of the blkptr and maintaining logical-size (aka. pre-compression) for each object. Also, we added an additional field in the user/group quota entries to maintain the logical consumption. Application of the quota is controlled by a dataset level property. | We worked on supporting this using the ASIZE of the blkptr and maintaining logical-size (aka. pre-compression) for each object. Also, we added an additional field in the user/group quota entries to maintain the logical consumption. Application of the quota is controlled by a dataset level property. | ||
== VDEV Properties (Allan Jude) == | == VDEV Properties (Allan Jude, Mark Maybee) == | ||
The ZFS properties interface is a powerful and expressive administrative interface, already used for datasets, snapshots, and pools. This work extends that paradigm to VDEVs as well. | The ZFS properties interface is a powerful and expressive administrative interface, already used for datasets, snapshots, and pools. This work extends that paradigm to VDEVs as well. | ||
This talk will discuss the finalized version of the concept and include recent work to implement queuing for device removals via VDEV properties. | This talk will discuss the finalized version of the concept and include recent work to implement queuing for device removals via VDEV properties. | ||
Other uses include exposing more statistics about vdevs, and in the future, possibly moving some tunables to be per-vdev (vdev queues, aggregation, etc). | Other uses include exposing more statistics about vdevs, and in the future, possibly moving some tunables to be per-vdev (vdev queues, aggregation, etc). | ||
The talk will also cover the new functionality of the “allocatable” property, for disabling allocations/writes on certain vdevs. | The talk will also cover the new functionality of the “allocatable” property, for disabling allocations/writes on certain vdevs. |