Lost+found directory – HP StoreAll Storage User Manual
Page 28
Description
Field
Allocation policy assigned on this file system. Defined policies are: ROUNDROBIN,
STICKY, DIRECTORY, LOCAL, RANDOM, and NONE. See
for information on these policies.
Default policy
The first segment to which an allocation policy is applied in a file system. If a segment
is not specified, allocation starts on the segment with the most storage space available.
Default start segment
NA.
File replicas
NA.
Dir replicas
Possible root segment inodes. This value is used internally.
Mount Options
Current root segment number, if known. This value is used internally.
Root Segment Hint
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 X9000 Software file systems, you will see a directory named
lost+found
. This directory is required for file system integrity and should not be deleted.
28
Maintaining file systems