HP StoreAll Storage - Manual (Page 38)

Description Field
Possible segment numbers for root segment replicas. This value is used internally. Root Segment Replica(s) Hint
Snapshot strategy, if defined. Snap FileSystem Policy
The following table lists the per-segment output fields reported by ibrix_fs -i.
Description Field
Number of segments. SEGMENT
The host that owns the segment. OWNER
Logical volume name. LV_NAME
The current state of the segment (for example, OK or UsageStale). STATE
Default block size, in KB. BLOCK_SIZE
Size of the segment, in GB. CAPACITY (GB)
Free space on this segment, in GB. FREE (GB)
Space available for user files, in GB. AVAIL (GB)
Inodes available on this segment. FILES
Free inodes available on this segment. FFREE
Percentage of total storage occupied by user files. USED%
Backup host name. BACKUP
Segment type. MIXED means the segment can contain both files and directories. TYPE
Tier to which the segment was assigned. TIER
Last time the segment state was reported. LAST_REPORTED
Host on which the file system is mounted. HOST_NAME
Host mountpoint. MOUNTPOINT
File system access privileges: RO or RW. PERMISSION
Specifies whether the root user is limited to read-only access, regardless of the access setting. Root_RO
Lost+found directory
When browsing the contents of IBRIX software file systems, you will see a directory named
lost+found
. This directory is required for file system integrity and should not be deleted. The
lost+found directory only exists at the top-level directory of a file system, which is also the
mountpoint. Additionally, there are several directories the you can see, at the top-level (mount
point) of a file system, that are "internal use only" and should not be deleted or edited. They are:
•
lost+found
•
.archiving
1
•
.audit
•
.webdav
1
There are a few exceptions in the .archiving directory. Some files in this directory are created
for user consumption in certain subdirectories of .archiving (described in various places in this
user guide, for example validation summary outputs 1–0.sum, and audit log reports), and those
specific files can be deleted if desired, but other files should not be deleted.
38 Maintaining file systems