Properties are described in alphabetical order.
Action
If Health is not
OK, this field shows recommended actions to take to resolve the health issue.
Alloc Size
The amount of space currently allocated to a virtual volume, or the total size of a linear volume.
Cache Opt
Shown by the details parameter. The cache optimization mode:
- standard: This controller cache mode of operation is optimized for sequential and random I/O and is the optimization of choice for most workloads. In this mode, the cache is kept coherent with the partner controller.
- no-mirror: In this mode of operation, the controller cache performs the same as the standard mode with the exception that the cache metadata is not mirrored to the partner. While this improves the response time of write I/O, it comes at the cost of redundancy. If this option is used, the user can expect higher write performance but is exposed to data loss if a controller fails.
Class
- Linear: The volume is in a linear pool.
- Virtual: The volume is in a virtual pool.
Desc
Shown by the
details parameter. Blank if not set.
Health
- OK
- Degraded
- Fault
- N/A
- Unknown
Large Virtual Extents
For a virtual volume, this shows whether the system will try to allocate pages in a sequentially optimized way to reduce I/O latency and improve performance.
- disabled or
off: Optimized page allocation is disabled. This is the default.
- enabled or
on: Optimized page allocation is enabled.
Name
The name of the volume.
Pool
The name of the pool that contains the volume.
Read Ahead
Shown by the
details parameter. The read-ahead cache setting:
- Disabled: Read-ahead is disabled.
- Adaptive: Adaptive read-ahead is enabled, which allows the controller to dynamically calculate the optimum read-ahead size for the current workload.
- Stripe: Read-ahead is set to one stripe. The controllers treat NRAID and RAID-1 disk groups internally as if they have a stripe size of 512 KB, even though they are not striped.
- 512 KB, 1 MB, 2 MB, 4 MB, 8 MB, 16 MB, or
32 MB: Size selected by a user.
Reason
If Health is not OK, this field shows the reason for the health state.
Role
Shown by the
details parameter.
- Copy Source: The volume is the source for a volume copy operation.
- Copy Destination: The volume is the destination for a volume copy operation.
- Primary: The volume is the primary volume in a replication set.
- Secondary: The volume is the secondary volume in a replication set.
- (blank): Not applicable.
Serial Number
Shown by the details parameter. The serial number of the volume.
Size
The total size of the volume.
Snap-Pool
Shown by the
details parameter. Not applicable.
Snap Retention Priority
Shown by the
details parameter. The retention priority for snapshots of the volume.
- never-delete: Snapshots will never be deleted.
- high: Snapshots may be deleted after all eligible medium-priority snapshots have been deleted.
- medium: Snapshots may be deleted after all eligible low-priority snapshots have been deleted.
- low: Snapshots may be deleted.
Snapshots that are mapped or are not leaves of a volume's snapshot tree are not eligible for automatic deletion.
Tier Affinity
Shown by the
details parameter.
- No Affinity: This setting uses the highest available performing tiers first and only uses the Archive tier when space is exhausted in the other tiers. Volume data will swap into higher performing tiers based on frequency of access and tier space availability.
- Archive: This setting prioritizes the volume data to the least performing tier available. Volume data can move to higher performing tiers based on frequency of access and available space in the tiers.
- Performance: This setting prioritizes volume data to the higher performing tiers. If no space is available, lower performing tier space is used. Performance affinity volume data will swap into higher tiers based upon frequency of access or when space is made available.
Total Size
The total size of the volume.
Type
- base: Base volume
- standard: Standard volume
Vdisk
The name of the vdisk that contains the volume.
WR Policy
Shown by the
details parameter. The cache write policy:
- write-back: Write-back caching does not wait for data to be completely written to disk before signaling the host that the write is complete. This is the preferred setting for a fault-tolerant environment because it improves the performance of write operations and throughput.
- write-through: Write-through caching significantly impacts performance by waiting for data to be completely written to disk before signaling the host that the write is complete. Use this setting only when operating in an environment with low or no fault tolerance.
WWN
Shown by the
details parameter. The World Wide Name of the volume
|