volume select snapshot select show

Displays details about the selected snapshot or connections to the snapshot.

Format

volume select vol_name snapshot select snap_name show [connections]

Variables 

vol_name

Name of a volume.

snap_name

Name of a snapshot.

Example

The following command displays detailed information about a snapshot:

> volume select newvol2 snapshot select inst-snap show

__________________________ Snapshot Information _________________________

Name: inst-snap                       Permission: read-only

DesiredStatus: online                 Status: online

OriginalVolumeSize: 5GB               CreationTime: 2006-06-14:17:16:39

Schedule:                             Replicate:

iSCSI Alias:                          iSCSI Name:

  NewVol2-2006-06-14-17:16:39.45       iqn.2001-05.com.equallogic:6-8a0900-

Description:                           cb76d4a01-40405000001af44907-newvol2

Connections: 0                         -2006-06-14-17:16:39.45

SnapsetName:

_________________________________________________________________________

The Status field displays the current snapshot status, as described in Table 11: Current Snapshot Status. The requested status (DesiredStatus field) is set by an administrator and described in Table 12: Requested Snapshot Status.

Table 11: Current Snapshot Status

Status

Description

online

Administrator set the snapshot online. Authorized hosts can access the snapshot, and no failures have occurred.

offline

Administrator set the snapshot offline. Hosts cannot access the snapshot, but no failures have occurred.

offline-lost-blocks

Snapshot was automatically set offline because lost blocks have occurred. Hosts cannot access the snapshot.

Note: To correct this condition, choose how to handle the lost blocks. See volume select snapshot select for more information.

offline-inconsistent

Snapshot was automatically set offline due to data inconsistencies. Contact your array support provider for information on how to proceed.

offline-member-down

Snapshot was automatically set offline because a member that contains snapshot data is down or cannot be accessed by the other members over the network. Hosts cannot access the snapshot.

Note: To correct this condition, fix the problem that caused the member to go down or become unreachable on the network.

offline-nospace-auto-grow

Thin-provisioned volume and its snapshots were automatically set offline because there is not enough free space in the pool for the volume reserve to grow.

Note: To correct this condition, add more space to the pool (such as by adding another member to the pool).

offline-snap-reserve-met

Snapshot was automatically set offline because the reserved snapshot space has been exceeded and the snapshot recovery policy dictates that the snapshots be set offline. Hosts cannot access the snapshot.

Note: To correct this condition, increase the amount of reserved snapshot space. See volume select .

offline-thin-max-grow-met

Volume and its snapshots were set offline because the in-use volume reserve reached the maximum in-use value.

Note: To correct this condition, increase the value of the maximum in-use space level for the volume (see volume select ), or increase the volume size.

Table 12: Requested Snapshot Status

Status

Description

online

Administrator set the snapshot online. Authorized hosts can access the snapshot.

offline

Administrator set the snapshot offline. Hosts cannot access the snapshot.

online-lost-blocks

Administrator set the snapshot online, despite lost blocks.

Authorized hosts can access the snapshot. If an application attempts to read a lost block, an error will occur. If the block is rewritten, no error will occur, and the block will no longer be marked lost.