From this page you can create, modify, view, and delete volume groups and logical volumes. You can copy and clone the logical volumes. You can also change the QoS settings of any volume from standard to enhanced.
Lists the names of the logical volumes and the names of the volume groups that are configured on this Oracle FS System. If a logical volume belongs to a volume group, the volume is listed beneath that group.
Indicates that the volume is fully accessible.
Indicates that the volume is not accessible.
Indicates that the write‑back cache of the volume is disabled, which reduces system performance. A Conservative state might indicate a hardware problem.
Indicates that the storage resources for the volume are reserved for the clone, but the clone is not committed to the storage device.
Indicates that the volume is in write protect mode and is set to read‑only.
Indicates that not enough information is obtained from the volume to report its status.
For LUNs, this amount is the same as the allocated amount.
Identifies the total amount of storage capacity that is reserved for this volume or this volume group.
Identifies the capacity limit to which the volume can grow.
Displays a graphical comparison of the allocated capacity that this volume uses to the unused allocated capacity.
Identifies the sum of the addressable capacity for the logical volume and its clone repository.
Identifies the amount of clone capacity that is allocated to the volume for clone data. The amount of capacity includes the overhead that is needed to create the logical volume. The overhead is parity for data protection.
Identifies the total amount of clone capacity that the system reserved for the logical volume. The amount of capacity includes the overhead that is needed to create the logical volume.
Identifies the maximum clone capacity allowed. For clones. This field identifies how much space is available for clone data.
Indicates that, in addition to the actual data, one set of parity bits exists for the logical volume. This parity level protects against the loss of one drive. Single parity is implemented as a variant of the RAID 5 storage technology.
Indicates that, in addition to the actual data, two sets of parity bits exist for the logical volume. This parity level protects against the loss of one or two drives with a slight cost to write performance. Double parity is implemented as a variant of the RAID 6 storage technology.
Indicates that no parity bits exist for the volume. Instead, the system writes the data in two different locations. This RAID level protects against the loss of at least one drive and possibly more drives with an improvement of the performance of random write operations. Mirrored RAID is implemented as a variant of the RAID 10 storage technology.
Indicates the highest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the highest priority when the system migrates the data to the higher-performing storage tiers.
Indicates the next highest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the next highest priority when the system migrates the data to the higher-performing storage tiers.
Indicates an intermediate priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive an intermediate priority when the system migrates the data to the higher-performing storage tiers.
Indicates the next to lowest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the next to lowest priority when the system migrates the data to the higher-performing storage tiers.
Indicates the lowest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the lowest priority when the system migrates the data to the higher-performing storage tiers.