text: The following types of thin-provisioned volumes are available: 
  
  (cid:2)*Autoexpand volumes*allocate real capacity from a storage pool on demand, which 
  
  minimizes required user intervention. However, a malfunctioning application can cause a 
  volume to expand until its real capacity is equal to the virtual capacity, which potentially 
  can starve other thin provisioned volumes in the pool. 
  
  (cid:2)*Non-autoexpand volumes*have a fixed amount of assigned real capacity. In this case, the 
  
  user must monitor the volume and assign more capacity when required. Although it 
  prevents starving other thin provisioned volumes, it introduces a risk of an unplanned 
  outage. A thin-provisioned volume goes offline if host tries to write more data than what 
  can fit into the allocated real capacity. 
  
  The main risk that is associated with using thin-provisioned volumes is running out of real 
  capacity in the storage volumes, pool, or both, and the resulting unplanned outage. Therefore, 
  strict monitoring of the used capacity on all non-autoexpand volumes and monitoring of the 
  free space in the storage pool is required. 
  
  When you configure a thin-provisioned volume, you can define a warning level attribute to 
  generate a warning event when the used real capacity exceeds a specified amount or 
  percentage of the total virtual capacity. You can also use the warning event to trigger other 
  actions, such as taking low-priority applications offline or migrating data into other storage 
  pools. 