IBM XIV User Manual

The local volume must be formatted.
If create_vol is specified as yes, the volume is created. In this case the size of the
newly created volume is identical to the size of the source volume. When creating
a volume, a pool name must be specified. Creating a volume fails if there is no
connectivity to the target since the volume's size is unknown.
Access Control:
User Category Permission
Storage administrator Allowed
Storage integration administrator Allowed
Application administrator Disallowed
Security administrator Disallowed
Read-only users Disallowed
Technicians Disallowed
Completion Codes:
v VOLUME_BAD_NAME
Volume name does not exist
v TARGET_BAD_NAME
Target name does not exist
v VOLUME_IS_SNAPSHOT
Operation is not permitted on snapshots
v VOLUME_HAS_MIRROR
Mirror is defined for this volume
v VOLUME_BELONGS_TO_CG
Volume belongs to a Consistency Group
v VOLUME_HAS_DATA_MIGRATION
Data Migration is defined for this volume
v VOLUME_HAS_SNAPSHOTS
Volume has snapshots
v VOLUME_NOT_FORMATTED
Local volume is not formatted
v TOO_MANY_MIRRORS
Maximum number of remote volumes (mirror/migration) is already defined
Troubleshooting: Delete remote mirrors or Data Migration objects
v VOLUME_EXISTS
Volume name already exists
v POOL_DOES_NOT_EXIST
Storage Pool does not exist
v VOLUME_BAD_PREFIX
Volume name has a reserved prefix
v NOT_ENOUGH_SPACE
No space to allocate volume
v NOT_ENOUGH_HARD_SPACE
No space to allocate for volume's current usage
242 IBM XIV Storage System User Manual

IBM XIV Specifications

General

Power Supply	Redundant power supplies
Drive Type	SATA
Redundancy	Fully redundant components
Connectivity	Fibre Channel, iSCSI
Form Factor	Rack-mounted
Cache	Distributed cache across modules
Data Protection	Snapshots, remote mirroring
Performance	High throughput and low latency
Scalability	Modular, scale-out architecture
Cooling	Redundant cooling
Architecture	Grid-based, distributed architecture