You can create a fileset to partition a file system for administrative operations at a
finer granularity than the entire file system.
You can create the following two types of filesets:
- Independent filesets
- Dependent filesets
A dependent fileset cannot be changed into an independent fileset, or vice versa. Independent
filesets have all the capabilities of a dependent fileset.
Perform the following steps to create a fileset:
-
Go to
page in the IBM Storage Scale GUI.
- Click Create Fileset. The Create Fileset
window appears.
- Select Basic or Custom in the Create
Fileset window. By using the Basic option, you can define only the basic
attributes of the fileset. In the Custom mode, you can define the inode number
and access control list for the fileset. Additionally, in the Custom mode, you
can choose whether the new fileset must be added to existing ILM policy rules with fileset scope.
Note: As the Custom mode contains more options, this procedure explains how to
create a fileset in the Custom mode.
- Click Browse to select the path of the junction in the Junction
path field. The junction path must be on one of the file systems and it must not refer to any
existing file or directory.
- In the Name field, type the name of the fileset.
- In the Comment field, type the comments, if any.
- Select either Independent or Dependent from
the Type field.
An independent fileset has a separate inode space
but shares physical storage with the remainder of the file system. Maximum number of inodes and
preallocation of inodes for an independent fileset can be specified while creating the fileset. A
dependent fileset shares the inode space and snapshot capability of the containing independent
fileset.
- In the Maximum number of inodes field, specify the maximum number
of file system objects such as files, directories, or links that can be stored under the independent
fileset, including that of the related child filesets.
- In the Allocated number of inodes field, specify the number of
inodes that is allocated when the fileset is created. The maximum allowed inodes cannot be less
than the allocated number.
- Click Edit in the Edit Action Control
section to define access control list for the users who can access the fileset.
Note: Only NFSv4 ACL semantics are supported in the GUI. The Edit Access Control section is not
shown when creating filesets in a file system that supports only POSIX ACL.
- Select the archive mode to be used from the options that are available under the
Archive Mode section.
The Archive Mode or the integrated archive
mode (IAM) mode provides control to prevent files from being changed or deleted unexpectedly. You
can set this option either while creating a fileset or when you modify it. The following options are
available to set the archive mode of a fileset. The available values are listed in the order of
increasing the level of restriction:
- Off: No immutability mode is set and the fileset behaves like a regular
fileset. This is the default value.
- Advisory: Allows setting retention times and WORM protection, but files
can be deleted based on the file permissions.
- Non-Compliant: In addition to the restrictions in the advisory mode,
files cannot be deleted if the retention time has not expired. However, retention times can be
reset, and files can be deleted but not changed.
- Compliant: In addition to the restrictions in the non-compliant mode,
retention time cannot be reset. When the retention time has expired, files can be deleted but not
changed.
- Compliant Plus: In addition to the restrictions in the compliant mode,
renaming of empty directories is not allowed.
- Click Create.
Fileset is created and linked to the junction path. You can see the newly created fileset in
the fileset table.