This guide describes how to configure and manage IBRIX software file systems and how to use NFS, SMB, FTP, and HTTP to
access file system data. The guide also describes the following file system features: quotas, remote replication, snapshots, data
retention and validation, data tiering, and file allocation. The guide is intended for system administrators managing 9300
Storage Gateway, 9320 Storage, 9720 Storage, and 9730 Storage. For the latest IBRIX guides, browse to
nl
http://www.hp.com/support/IBRIXManuals.
HP Part Number: TA768-96076
Published: December 2012
Edition: 9
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Revision History
DateEdition
DescriptionSoftware
Version
Initial release of HP 9000 File Serving Software5.3.1November 20091
Updated license and quotas information5.3.2December 20092
5.4.0April 20103
Added information about file cloning, CIFS, directory tree quotas, the Statistics tool,
and GUI procedures
Removed information about the Statistics tool5.4.1July 20104
5.5.0December 20105
Added information about authentication, CIFS, FTP, HTTP, SSL certificates, and remote
replication
Updated CIFS, FTP, HTTP, and snapshot information5.6April 20116
6.0September 20117
Added or updated information about data retention and validation, software snapshots,
block snapshots, remote replication, HTTP, case insensitivity, quotas
6.1June 20128
Added or updated information about file systems, file share creation, rebalancing
segments, remote replication, user authentication, CIFS, LDAP, data retention, data
tiering, file allocation, quotas, Antivirus software
6.2December 20129
Added or updated information about file systems, physical volumes, segment
rebalancing, remote replication, Antivirus scans, REST API, Express Query, auditing,
HTTP, quotas, data tiering, renamed CIFS to SMB
Contents
1 Using IBRIX software file systems...................................................................9
File system operations................................................................................................................9
File system building blocks.......................................................................................................11
The following diagram highlights the operating principles of the IBRIX file system.
The topology in the diagram reflects the architecture of the HP 9320, which uses a building block
of server pairs (known as couplets) with SAS attached storage. In the diagram:
•There are four file serving nodes, SS1–SS4. These nodes are also called segment servers.
•SS1 and SS2 share access to segments 1–4 through SAS connections to a shared storage
array.
•SS3 and SS4 share access to segments 5-8 through SAS connections to a shared storage
array.
•One client is accessing the name space using NAS protocols.
•One client is using the proprietary IBRIX client.
The following steps correspond to the numbering in the diagram:
1.The “namespace” of the file system is a collection of segments. Each segment is simply a
repository for files and directories with no implicit namespace relationships among them.
File system operations9
(Specifically, a segment need not be a complete, rooted directory tree). Segments can be any
size and different segments can be different sizes.
2.The location of files and directories within particular segments in the file space is independent
of their respective and relative locations in the namespace. For example, a directory (Dir1)
can be located on one segment, while the files contained in that directory (File1 and File2)
are resident on other segments. The selection of segments for placing files and directories is
done dynamically when the file/directory is created, as determined by an allocation policy.
The allocation policy is set by the system administrator in accordance with the anticipated
access patterns and specific criteria relevant to the installation (such as performance and
manageability). The allocation policy can be changed at any time, even when the file system
is mounted and in use. Files can be redistributed across segments using a rebalancing utility.
For example, rebalancing can be used when some segments are too full while other have free
capacity, or when files need to be distributed across new segments.
3.Segment servers are responsible for managing individual segments of the file system. Each
segment is assigned to one segment server and each server may own multiple segments, as
shown by the color coding in the diagram. Segment ownership can be migrated between
servers with direct access to the storage volume while the file system is mounted. For example,
Seg1 can be migrated between SS1 and SS2 but not to SS3 or SS4.
Additional servers can be added to the system dynamically to meet growing performance
needs, without adding more capacity, by distributing the ownership of existing segments for
proper load balancing and utilization of all servers. Conversely, additional capacity can be
added to the file system while in active use without adding more servers—ownership of the
new segments is distributed among existing servers. Servers can be configured with failover
protection, with other servers being designated as standby servers that automatically take
control of a server’s segments if a failure occurs.
4.Clients run the applications that use the file system. Clients can access the file system either
as a locally mounted cluster file system using the IBRIX Client or using standard network
attached storage (NAS) protocols such as NFS and Server Message Block (SMB).
5.Use of the IBRIX Client on a client system has some significant advantages over the NAS
approach—specifically, the IBRIX Client driver is aware of the segmented architecture of the
file system and, based on the file/directory being accessed, can route requests directly to the
correct segment server, yielding balanced resource utilization and high performance. However,
the IBRIX Client is available only for a limited range of operating systems.
6.NAS protocols such as NFS and SMB offer the benefits of multi-platform support and low cost
of administration of client software, as the client drivers for these protocols are generally
available with the base operating system. When using NAS protocols, a client must mount
the file system from one (or more) of the segment servers. As shown in the diagram, all requests
are sent to the server from which the share is mounted, which then performs the required
routing.
7.Any segment server in the namespace can access any segment. There are three cases:
a.Selected segment is owned by the segment server initiating the operation (for example,
SS1 accessing Seg1).
b.Selected segment is owned by another segment server but is directly accessible at the
block level by the segment server initiating the operation (for example, SS1 accessing
Seg3).
c.Selected segment is owned by another segment server and is not directly accessible by
the segment server initiating the operation (for example, SS1 accessing Seg5).
Each case is handled differently. The data paths are shown in heavy red broken lines in the
diagram:
a.The segment server initiating the operation services the read or write request to the local
segment.
b.In this case, reads and writes take different routes:
10Using IBRIX software file systems
1)The segment server initiating the operation can read files directly from the segment
across the SAN; this is called a SAN READ.
2)The segment server initiating the operation routes writes over the IP network to the
segment server owning the segment. That server then writes data to the segment.
c.All reads and writes must be routed over the IP network between the segment servers.
8.Step 7 assumed that the server had to go to a segment to read a file. However, every segment
server that reads a file keeps a copy of it cached in its memory regardless of which segment
it was read from (in the diagram, two servers have cached copies of File 1). The cached
copies are used to service local read requests for the file until the copy is made invalid, for
example, because the original file has been changed. The file system keeps track of which
servers have cached copies of a file and manages cache coherency using delegations, which
are IBRIX file system metadata structures used to track cached copies of data and metadata.
File system building blocks
A file system is created from building blocks. The first block comprises the underlying physical
volumes, which are combined in volume groups. Segments (logical volumes) are created from the
volume groups. The built-in volume manager handles all space allocation considerations involved
in file system creation.
Configuring file systems
You can configure your file systems to use the following features:
•Quotas. This feature allows you to assign quotas to individual users or groups, or to a directory
tree. Individual quotas limit the amount of storage or the number of files that a user or group
can use in a file system. Directory tree quotas limit the amount of storage and the number of
files that can be created on a file system located at a specific directory tree. See “Configuring
quotas” (page 25).
•Remote replication. This feature provides a method to replicate changes in a source file system
on one cluster to a target file system on either the same cluster or a second cluster. See “Using
remote replication” (page 127).
File system building blocks11
•Data retention and validation. Data retention ensures that files cannot be modified or deleted
for a specific retention period. Data validation scans can be used to ensure that files remain
unchanged. See “Managing data retention” (page 143).
•Antivirus support. This feature is used with supported Antivirus software, allowing you to scan
files on an IBRIX file system. See “Configuring Antivirus support” (page 192).
•IBRIX software snapshots. This feature allows you to capture a point-in-time copy of a file
system or directory for online backup purposes and to simplify recovery of files from accidental
deletion. Users can access the file system or directory as it appeared at the instant of the
snapshot. See “Creating IBRIX software snapshots” (page 204).
•Block Snapshots. This feature uses the array capabilities to capture a point-in-time copy of a
file system for online backup purposes and to simplify recovery of files from accidental deletion.
The snapshot replicates all file system entities at the time of capture and is managed exactly
like any other file system. See “Creating block snapshots” (page 213).
•Data tiering. This feature allows you to set a preferred tier where newly created files will be
stored. You can then create a tiering policy to move files from initial storage, based on file
attributes such as such as modification time, access time, file size, or file type. See “Using
data tiering” (page 225).
•File allocation. This feature allocates new files and directories to segments according to the
allocation policy and segment preferences that are in effect for a client. An allocation policy
is an algorithm that determines the segments that are selected when clients write to a file
system. See “Using file allocation” (page 240).
Accessing file systems
Clients can use the following standard NAS protocols to access file system data:
•NFS. See “Using NFS” (page 51) or more information.
•SMB. See “Using SMB” (page 73) for more information.
•FTP. See “Using FTP” (page 98) for more information.
•HTTP. See “Using HTTP” (page 108) for more information.
You can also use IBRIX 9000 clients to access file systems. Typically, these clients are installed
during the initial system setup. See the HP IBRIX 9000 Storage Installation Guide for more
information.
12Using IBRIX software file systems
2 Creating and mounting file systems
This chapter describes how to create file systems and mount or unmount them.
Creating a file system
You can create a file system using the New Filesystem Wizard provided with the GUI, or you can
use CLI commands. The New Filesystem Wizard also allows you to create an NFS export or an
SMB share for the file system.
Using the New Filesystem Wizard
To start the wizard, click New on the Filesystems top panel. The wizard includes several steps and
a summary, starting with selecting the storage for the file system.
NOTE:For details about the prompts for each step of the wizard, see the GUI online help.
On the Select Storage dialog box, select the storage that will be used for the file system.
Configure Options dialog box. Enter a name for the file system, and specify the appropriate
configuration options.
Creating a file system13
WORM/Data Retention dialog box. If data retention will be used on the file system, enable it and
set the retention policy. See “Managing data retention” (page 143) for more information.
14Creating and mounting file systems
You can configure the following:
•Default retention period. This period determines whether you can manage WORM
(non-retained) files as well as WORM-retained files. (WORM (non-retained) files can be deleted
at any time; WORM-retained files can be deleted only after the file's retention period has
expired.)
To manage only WORM-retained files, set the default retention period to a non-zero value.
WORM-retained files then use this period by default; however, you can assign a different
retention period if desired.
To manage both WORM (non-retained) and WORM-retained files, uncheck Set Default RetentionPeriod. The default retention period is then set to 0 seconds. When you make a WORM file
retained, you will need to assign a retention period to the file.
•Autocommit period. When the autocommit period is set, files become WORM or
WORM-retained if they are not changed during the period. (If the default retention period is
set to zero, the files become WORM. If the default retention period is set to a value greater
than zero, the files become WORM-retained.) To use this feature, check Set Auto-CommitPeriod and specify the time period. The minimum value for the autocommit period is five
minutes, and the maximum value is one year. If you plan to keep normal files on the file system,
do not set the autocommit period.
•Data validation. Select this option to schedule periodic scans on the file system. Use the default
schedule, or click Modify to open the Data Validation Scan Schedule dialog box and configure
your own schedule.
•Report Data Generation. Select this option if you want to create data retention reports. Use
the default schedule, or click Modify to open the Report Data Generation Schedule dialog
box and configure your own schedule.
Creating a file system15
•Express Query. Check this option to enable StoreAll Express Query on the file system. Express
Query is a database used to record metadata state changes occurring on the file system.
Auditing Options dialog box. If you enabled Express Query on the WORM/Data Retention dialog
box, you can also enable auditing and select the events that you want to log.
16Creating and mounting file systems
Default File Shares dialog box. Use this dialog box to create an NFS export and/or an SMB share
at the root of the file system. The default settings are used. See “Using NFS” (page 51) and “Using
SMB” (page 73) for more information.
Review the Summary to ensure that the file system is configured properly. If necessary, you can
return to a dialog box and make any corrections.
Configuring additional file system options
The New Filesystem wizard creates the file system with the default settings for several options. You
can change these settings on the Modify Filesystem Properties dialog box, and can also configure
data retention, data tiering, and file allocation. To open the dialog box, select the file system on
the Filesystems panel. Select Summary from the lower Navigator, and then click Modify on the
Summary panel.
The General tab allows you to enable or disable quotas, Export Control, and 32-bit compatibility
mode on the file system.
When Export Control is enabled on a file system, by default, IBRIX 9000 clients have no access
to the file system. Instead, the system administrator grants the clients access by executing the
ibrix_mount command. Export Control affects only for NFS access for IBRIX 9000 clients.
Enabling Export Control does not affect access from a file serving node to a file system. File serving
nodes always have RW access.
By default, file systems are created in 64-bit mode. If clients need to run a 32-bit application, you
can enable 32-bit compatibility mode. This option is applied to the file system at mount time and
can be enabled or disabled as necessary.
Creating a file system17
The Data Retention tab allows you to change the data retention configuration. The file system must
be unmounted. See “Configuring data retention on existing file systems” (page 147) for more
information.
NOTE:Data retention cannot be enabled on a file system created on IBRIX software 5.6 or earlier
versions until the file system is upgraded.
The Allocation, Segment Preference, and Host Allocation tabs are used to modify file allocation
policies and to specify segment preferences for file serving nodes and IBRIX 9000 clients. See
“Using file allocation” (page 240) for more information.
Creating a file system using the CLI
The ibrix_fs command is used to create a file system. It can be used in the following ways:
•Create a file system with the specified segments (segments are logical volumes):
In the commands, the –t option specifies a tier. TIERNAME can be any alphanumeric, case-sensitive,
text string. Tier assignment is not affected by other options that can be set with the ibrix_fs
command.
NOTE:A tier is created whenever a segment is assigned to it. Be careful to spell the name of the
tier correctly when you add segments to an existing tier. If you make an error in the name, a new
tier is created with the incorrect tier name, and no error is recognized.
Options for data retention
OptionFeature
Data
retention
Query
The following example enables data retention, Express Query, and auditing, with all events being
audited:
ibrix_fs -o "retenMode=Enterprise,retenDefPeriod=5m,retenMinPeriod=2,
retenMaxPeriod=30y,retenAutoCommitPeriod=1d" –T –E -A –oa
audit_mode=on,all=on c -f ifs1 -s ilv_[1-4] -a
-A -oa OPTION1=VALUE1[,OPTION2=VALUE2,...]Auditing
Creating a file system manually from physical volumes
This procedure is equivalent to using ibrix_fs to create a file system from physical volumes in
a single step. Instead of a single command, you build the file system components individually:
1.Discover the physical volumes in the system. Use the ibrix_pv command.
2.Create volume groups from the discovered physical volumes. Use the ibrix_vg command.
3.Create logical volumes (also called segments) from volume groups. Use the ibrix_lv
command.
4.Create the file system from the new logical volumes. Use the ibrix_fs command.
See the HP IBRIX 9000 Storage CLI Reference Guide for details about these commands.
File limit for directories
The maximum number of files in a directory depends on the length of the file names, and also the
names themselves. The maximum size of a directory is approximately 4 GB (double indirect blocks).
An average file name length of eight characters allows about 12 million entries. However, because
directories are hashed, it is unlikely that a directory can contain this number of entries. Files with
a similar naming pattern are hashed into the same bucket. If that bucket fills up, another file cannot
be created there, even if free space is available elsewhere in the directory. If you try to create
another file with a different name, it may succeed, but randomly.
Managing mountpoints and mount/unmount operations
GUI procedures
When you use the New Filesystem Wizard to create a file system, you can specify a name for the
mountpoint and indicate whether the file system should be mounted after it is created. The wizard
will create the mountpoint if necessary. The Filesystems panel shows the file systems created on
the cluster.
To view the mountpoint information for a file system, select the file system on the Filesystems panel,
and click Mountpoints in the lower Navigator. The Mountpoints panel shows the hosts that have
File limit for directories19
mounted the file system, the name of the mountpoint, the access (RW or RO) allowed to the host,
and whether the file system is mounted.
To mount or remount a file system, select it on the Filesystems panel and click Mount. You can
select several mount options on the Mount Filesystem dialog box. To remount the file system, click
remount.
The available mount options are:
•atime: Update the inode access time when a file is accessed
NOTE:If you do not specifically set atime as an option, noatime is set instead and the
inode access time is not updated when the file is accessed. There is not an option to specifically
set noatime as an option.
•nodiratime: Do not update the directory inode access time when the directory is accessed
20Creating and mounting file systems
•nodquotstatfs: Disable file system reporting based on directory tree quota limits
•path: For IBRIX 9000 clients only, mount on the specified subdirectory path of the file system
instead of the root.
•remount: Remounts a file system without taking it offline. Use this option to change the current
mount options on a file system.
You can also view mountpoint information for a particular server. Select that server on the Servers
panel, and select Mountpointsfrom the lower Navigator. To delete a mountpoint, select that
mountpoint and click Delete.
CLI procedures
The CLI commands are executed immediately on file serving nodes. For IBRIX 9000 clients, the
command intention is stored in the active Fusion Manager. When IBRIX software services start on
a client, the client queries the active Fusion Manager for any commands. If the services are already
running, you can force the client to query the Fusion Manager by executing either ibrix_client
or ibrix_lwmount -a on the client, or by rebooting the client.
If you have configured hostgroups for your IBRIX 9000 clients, you can apply a command to a
specific hostgroup. For information about creating hostgroups, see the administration guide for
your system.
Creating mountpoints
Mountpoints must exist before a file system can be mounted. To create a mountpoint on file serving
nodes and IBRIX 9000 clients, enter the following command:
ibrix_mountpoint -c [-h HOSTLIST] -m MOUNTPOINT
To create a mountpoint on a hostgroup , enter the following command:
ibrix_mountpoint -c -g GROUPLIST -m MOUNTPOINT
For information about mountpoint options, see the "ibrix_mountpoint" section in the HP IBRIX 9000
CLI Reference Guide.
Deleting mountpoints
Before deleting mountpoints, verify that no file systems are mounted on them. To delete a mountpoint
from file serving nodes and IBRIX 9000 clients, use the following command:
ibrix_mountpoint -d [-h HOSTLIST] -m MOUNTPOINT
Managing mountpoints and mount/unmount operations21
To delete a mountpoint from specific hostgroups, use the following command:
ibrix_mountpoint -d -g GROUPLIST -m MOUNTPOINT
Viewing mountpoint information
To view mounted file systems and their mountpoints on all nodes, use the following command:
ibrix_mountpoint -l
Mounting a file system
File system mounts are managed with the ibrix_mount command. The command options and
the default file system access allowed for IBRIX 9000 clients depend on whether the optional Export
Control feature has been enabled on the file system (see “Using Export Control” (page 24) for
more information). This section assumes that Export Control is not enabled, which is the default.
NOTE:A file system must be mounted on the file serving node that owns the root segment (that
is, segment 1) before it can be mounted on any other host. IBRIX software automatically mounts a
file system on the root segment when you mount it on all file serving nodes in the cluster. The
mountpoints must already exist.
Mount a file system on file serving nodes and IBRIX 9000 clients:
ibrix_mount -f FSNAME [-o {RW|RO}] -g GROUP -m MOUNTPOINT
NOTE:If you do not include the -o parameter, the default access option for the mounted file
system is Read Write.
Unmounting a file system
Use the following commands to unmount a file system.
NOTE:Be sure to unmount the root segment last. Attempting to unmount it while other segments
are still mounted will result in failure. If the file system was exported using NFS, you must unexport
it before you can unmount it (see “Exporting a file system” (page 51)).
To unmount a file system from one or more file serving nodes, IBRIX 9000 clients, or hostgroups:
If clients are running 32-bit applications, you can enable 32-bit compatibility mode. This mode is
applied to the file system at mount time. You can enable or disable 32-bit compatibility on the
Modify Filesystems Properties dialog box, and can also use the following commands.
Enable 32-bit compatibility mode:
ibrix_fs_tune -c -e -f FSNAME
Disable 32-bit compatibility mode:
ibrix_fs_tune -c -d -f FSNAME
Mounting and unmounting file systems locally on IBRIX 9000 clients
On both Linux and Windows IBRIX 9000 clients, you can locally override a mount. For example,
if the Fusion Manager configuration database has a file system marked as mounted for a particular
client, that client can locally unmount the file system.
22Creating and mounting file systems
Linux IBRIX 9000 clients
To mount a file system locally, use the following command on the Linux 9000 client. A Fusion
Manager name (fmname) is required only if this 9000 client is registered with multiple Fusion
Managers.
To unmount a file system locally, use one of the following commands on the Linux 9000 client. The
first command detaches the specified file system from the client. The second command detaches
the file system that is mounted on the specified mountpoint.
Use the Windows 9000 client GUI to mount file systems locally. Click the Mount tab on the GUI
and select the cluster name from the list (the cluster name is the Fusion Manager name). Then, enter
the name of the file system, select a drive, and click Mount.
If you are using Remote Desktop to access the client and the drive letter is not displayed, log out
and log back in. This is a known limitation of Windows Terminal Services when exposing new
drives.
To unmount a file system on the Windows 9000 client GUI, click the Umount tab, select the file
system, and then click Umount.
Limiting file system access for IBRIX 9000 clients
By default, all IBRIX 9000 clients can mount a file system after a mountpoint has been created. To
limit access to specific IBRIX 9000 clients, create an access entry. When an access entry is in place
for a file system (or a subdirectory of the file system), it enters secure mode, and mount access is
restricted to clients specified in the access entry. All other clients are denied mount access.
Select the file system on the Filesystems top panel, and then select Client Exports in the lower
navigator. On the Create Client Export(s) dialog box, select the clients or hostgroups that will be
allowed access to the file system or a subdirectory of the file system.
To remove a client access entry, select the affected file system on the GUI, and then select Client
Exports from the lower Navigator. Select the access entry from the Client Exports display, and click
Delete.
On the CLI, use the ibrix_exportfs command to create an access entry:
When Export Control is enabled on a file system, by default, IBRIX 9000 clients have no access
to the file system. Instead, the system administrator grants the clients access by executing the
ibrix_mount command. Export Control affects only NFS access for IBRIX 9000 clients. Enabling
Export Control does not affect access from a file serving node to a file system. File serving nodes
always have RW access.
To determine whether Export Control is enabled, run ibrix_fs -i or ibrix_fs -l. The output
indicates whether Export Control is enabled.
To enable Export Control, include the -C option in the ibrix_fs command:
ibrix_fs -C -E -f FSNAME
To disable Export Control, execute the ibrix_fs command with the -C and -D options:
ibrix_fs -C -D -f FSNAME
To mount a file system that has Export Control enabled, include the ibrix_mount -o {RW|RO}
option to specify that all clients have either RO or RW access to the file system. The default is RO.
In addition, when specifying a hostgroup, the root user can be limited to RO access by adding
the root_ro parameter.
24Creating and mounting file systems
3 Configuring quotas
Quotas can be assigned to individual users or groups, or to a directory tree. Individual quotas
limit the amount of storage or the number of files that a user or group can use in a file system.
Directory tree quotas limit the amount of storage and the number of files that can be created on a
file system located at a specific directory tree. Note the following:
•You can assign quotas to a user, group, or directory on the GUI or from the CLI. You can also
import quota information from a file.
•If a user has a user quota and a group quota for the same file system, the first quota reached
takes precedence.
•Nested directory quotas are not supported. You cannot configure quotas on a subdirectory
differently than the parent directory.
•The existing quota configuration can be exported to a file at any time.
NOTE:HP recommends that you export the quota configuration and save the resulting file
whenever you update quotas on your cluster.
How quotas work
Quotas can be set for users, groups, or directories in a file system. A quota is specified by hard
and soft storage limits for both the megabytes of storage and the number of files allotted to the
user, group, or directory. The hard limit is the maximum storage (in terms of file size and number
of files) allotted to the user, group, or directory. The soft limit specifies the number of megabytes
or files that, when reached, starts a countdown timer.
If the megabytes of storage or number of files are not reduced below the soft limit, the timer runs
until either the hard storage limit is reached or the grace period for the timer elapses. (The default
grace period is seven days.) When the timer stops, the user, group, or directory for which the
quota was set cannot store any more data, and the system issues quota exceeded messages at
each write attempt.
NOTE:Quota statistics are updated on a regular basis (at one-minute intervals). At each update,
the file and storage usage for each quota-enabled user, group, or directory tree is queried, and
the result is distributed to all file serving nodes. Users or groups can temporarily exceed their quota
if the allocation policy in effect for a file system causes their data to be written to different file
serving nodes during the statistics update interval. In this situation, it is possible for the storage
usage visible to each file serving node to be below or at the quota limit while the aggregate storage
use exceeds the limit.
There is a delay of several minutes between the time a command to update quotas is executed
and when the results are displayed by the ibrix_edquota -l command. This is normal behavior.
Enabling quotas on a file system and setting grace periods
Before you can set quota limits, quotas must be enabled on the file system. You can enable quotas
on a file system at any time.
To view the current quotas configuration on the GUI, select the file system and then select Quotas
from the lower Navigator. The Quotas Summary panel specifies whether quotas are enabled and
lists the grace periods for blocks and inodes.
How quotas work25
To change the quotas configuration, click Modify on the Quota Summary panel.
On the CLI, run the following command to enable quotas on an existing file system:
ibrix_fs -q -E -f FSNAME
Setting quotas for users, groups, and directories
Before configuring quotas, the quota feature must be enabled on the file system and the file system
must be mounted.
NOTE:For the purpose of setting quotas, no UID or GID can exceed 2,147,483,647.
Setting user quotas to zero removes the quotas.
The Quota Management Wizard can be used to create, modify, or delete quotas for users, groups,
and directories in the selected file system. Click Quotas Wizard on the Quota Summary panel to
open the wizard. The Welcome dialog box describes the options available in the wizard.
26Configuring quotas
The User Quotas dialog box is used to create, modify, or delete quotas for users. To add a user
quota, enter the required information and click Add. Users having quotas are listed in the table at
the bottom of the dialog box. To modify quotas for a user, check the box preceding that user. You
can then adjust the quotas as needed. To delete quotas for a user, check the box and click Delete.
The Group Quotas dialog box is used to create, modify, or delete quotas for groups. To add a
group quota, enter the required information and click Add. The new quota applies to all users in
the group. Groups having quotas are listed in the table at the bottom of the dialog box. To modify
Setting quotas for users, groups, and directories27
quotas for a group, check the box preceding that group. You can then adjust the quotas as needed.
To delete quotas for a group, check the box and click Delete. group
The Directory Quotas dialog box is used to create, modify, or delete quotas for directories. To add
a directory quota, enter the required information and click Add. The Name (Alias) is a unique
identifier for the quota, and cannot include commas. The new quota applies to all users and groups
storing data in the directory. Directories having quotas are listed in the table at the bottom of the
dialog box. To modify quotas for a directory, check the box preceding that directory. You can
then adjust the quotas as needed. To delete quotas for a directory, check the box and click Delete.
28Configuring quotas
summary
Configuring quotas from the CLI
In the commands, use -M SOFT_MEGABYTES and -m HARD_MEGABYTES to specify soft and hard
limits for the megabytes of storage. Use -I SOFT_FILES and -i HARD_FILES to specify soft
and hard limits for the number of files allowed.
The -p PATH option specifies the pathname of the directory tree. If the pathname includes a space,
enclose the portion of the pathname that includes the space in single quotation marks, and enclose
the entire pathname in double quotation marks. For example:
-p "/fs48/data/'QUOTA 4'"
The -n NAME option specifies a unique name for the directory tree quota. The name cannot contain
a comma (,) or colon (:) character.
NOTE:When you create a directory quota, the system also runs ibrix_onlinequotacheck
command in DTREE_CREATE mode. If you are creating multiple directory quotas, you can import
the quotas from a file. The system then uses batch processing to create the quotas. If you add the
quotas individually, you will need to wait for ibrix_onlinequotacheck to finish after creating
each quota.
Using a quotas file
Quota limits can be imported into the cluster from the quotas file, and existing quotas can be
exported to the file. See “Format of the quotas file” (page 30) for the format of the file.
Importing quotas from a file
From the GUI, select the file system, select Quotas from the lower Navigator, and then click Import
on the Quota Summary panel.
Using a quotas file29
From the CLI, use the following command to import quotas from a file, where PATH is the path to
the quotas file:
ibrix_edquota -t -p PATH -f FSNAME
See “Format of the quotas file” (page 30) for information about the format of quota file.
Exporting quotas to a file
From the GUI, select the file system, select Quotas from the lower Navigator, and then click Export
on the Quota Summary panel.
From the CLI, use the following command to export the existing quotas information to a file, where
PATH is the pathname of the quotas file:
ibrix_edquota -e -p PATH -f FSNAME
Format of the quotas file
The quotas file contains a line for each user, group, or directory tree assigned a quota. When you
add quota entries, the lines must use one of the following formats. The “A” format specifies a user
or group ID. The “B” format specifies a user or group name, or a directory tree that has already
been assigned an identifier name. The “C” format specifies a directory tree, where the path exists,
but the identifier name for the directory tree will not be created until the quotas are imported.