beautypg.com

Accessing snapshot file systems – HP StoreAll Storage User Manual

Page 178

background image

The following table lists the output fields for ibrix_vs_snap -i.

Description

Field

Snapshot segment number.

SEGMENT

The file serving node that owns the snapshot segment.

OWNER

Logical volume.

LV_NAME

State of the snapshot.

STATE

Block size used for the snapshot.

BLOCK_SIZE

Size of this snapshot file system, in GB.

CAPACITY (GB)

Free space on this snapshot file system, in GB.

FREE (GB)

Space available for user files, in GB.

AVAIL (GB)

Number of files that can be created in this snapshot file system.

FILES

Number of unused file inodes available in this snapshot file system.

FFREE

Percentage of total storage occupied by user files.

USED%

Backup host name.

BACKUP

Segment type. Mixed means the segment can contain both directories and files.

TYPE

Tier to which the segment was assigned.

TIER

Last time the segment state was reported.

Last Reported

Accessing snapshot file systems

By default, snapshot file systems are mounted in two locations on the file serving nodes:

/

//.

For example, if you take a snapshot of the fs1 file system and name the snapshot fs1_snap1,
it will be mounted at /fs1_snap1 and at /fs1/.fs1_snap1.

X9000 clients must mount the snapshot file system (/) to access the contents
of the snapshot.

NFS and CIFS clients can access the contents of the snapshot through the original file system (such
as /fs1/.fs1_snap1) or they can mount the snapshot file system (in this example, /fs1_snap1).

The following window shows an NFS client browsing the snapshot file system .fs1_snap2 in the
fs1_nfs

file system.

178

Creating block snapshots