Administrator Guide

Status Description Solution
unavailable due to
SyncRep
Volume or snapshot is unavailable because
SyncRep is confused, often due to a mismatch
between the state in the database and the
expected state.
Determine the reason for the issue and correct
the problem.
available (no new
connections)
During a failover, SyncRep is trying to determine
which volume should be active. Until then, no
new connections are allowed.
Wait for SyncRep for to determine which
volume is active.
unavailable due to
internal error
Volume or snapshot is unavailable due to an
unexpected error.
Contact Customer Support for assistance.
Volume and Snapshot Requested Status
Table 36. Volume and Snapshot Requested Status shows the possible values for the requested status for a volume or snapshot.
Table 36. Volume and Snapshot Requested Status
Status Description
online
Administrator set the volume or snapshot online.
offline
Administrator set the volume or snapshot oine. Computers cannot access an oine volume or
snapshot.
online (lost blocks)
Administrator set the volume or snapshot online despite lost blocks. Authorized computers can
access the volume or snapshot.
If an application tries to read a lost block, an error occurs. If the block is rewritten, no error occurs,
and the block no longer shows a status of lost.
About Managing Storage Capacity Utilization On Demand (Thin
Provisioning)
You can use thin-provisioning technology to more eciently allocate storage space, while still meeting application and user storage
needs. With a thin-provisioned volume, the group allocates space based on volume usage, enabling you to “over-provision” group
storage space (provision more space than what is physically available).
However, if your environment requires guaranteed space for volume, thin provisioning might be inappropriate. Thin provisioning is
most eective if you can accurately predict how volume usage increases over time.
NOTE: Dell recommends that you fully understand the benets and risks of using thin provisioning before implementing it
in your environment. Environments that use thin provisioning should have around-the-clock support to handle any space
allocation issues and prevent service-level disruption.
Thin provisioning volumes is benecial in a number of environments. For example, if your environment does not easily allow you to
expand le systems or raw disks, you can give thin-provisioned volumes excessively large reported sizes to account for future
growth. The group automatically allocates space to volumes only if usage patterns warrant the space.
Thin provisioning also helps you plan for future group expansion. For example, you can size volumes according to their maximum
possible space requirements, even if the group currently cannot provide all the required space. As volume usage increases, you can
expand group capacity, with no user impact. You do not need to change drive letters, expand volume sizes, or add volumes.
When you create a volume, you specify the reported size for the volume. The reported size is seen by iSCSI initiators. The actual
amount of pool space that the group allocates to a volume is called the volume reserve. The value of the volume reserve depends on
whether you enable thin provisioning on a volume:
• Thin provisioning disabled
About Volumes
157