IBM Storwize FileSet Tasks

This chapter contains the following sections:

Delete IBM Storwize File Set

Summary
Delete IBM Storwize File Set
Description
This task deletes the selected file set. If the file set is linked it will be unlinked. If the file set contains any linked child file sets they are also unlinked. The task fails if the file set contains snapshots, the snapshots must be deleted prior deleting the file set. The root file set cannot be deleted.
Inputs
Input Description Mappable To Type Mandatory
File Set Choose an IBM Storwize file set to be deleted ibm​Storwize​File​Set​Identity Y
Deleting the file set also deletes all data that the file set contains Do you want to continue?
* To confirm, type YES Enter YES for recursive delete Y
Outputs
Output Description Type
IBM_​STORWIZE_​OUTPUT_​FILESET_​IDENTITY Output of file set identity ibm​Storwize​File​Set​Identity
IBM_​STORWIZE_​OUTPUT_​ACCOUNT_​NAME Output of infra account name account​Name
IBM_​STORWIZE_​OUTPUT_​FILESET_​NAME Output of file set name gen_​text_​input
IBM_​STORWIZE_​OUTPUT_​DATACENTER Output of datacenter name on which selected operation was performed datacenter​Name

New IBM Storwize File Set

Summary
New IBM Storwize File Set
Description
This task creates a new file set using the specified name. The file sets root can be anywhere in the directory structure of the parent file system. The sets include all files and directories above that junction point. When creating a file set, the base directory path must exist. However, the directory (or junction point) that is being defined must not exist already, because it is to be created as part of the file set creation process. You must also define the file set as either dependent or independent. A dependent file set shares the same file system and inode definitions as the parent independent file set that contains it. If set to independent, the file set has its own inode space. That allows for independent management, such as quotas. When a file system is created, an initial file set is also created automatically in the root directory.
Inputs
Input Description Mappable To Type Mandatory
Select Account Name Choose an IBM Storwize account account​Name Y
File Set Type Choose a file set type ibm​Storwize​File​Set​Type Y
Junction Path Choose the path.​ The junction path must be on one of the file systems and not refer to any existing file or directory.​ Example of a valid path: file_​system_​path/existing_​sub_​directory/new_​sub_​directory.​ Example of an invalid path: file_​system_​path/existing_​sub_​directory/new_​sub_​directory1/new_​sub_​directory2.​ The linking process cannot create more than one new subdirectory.​ ibm​Storwize​File​Set​Junction​Path​Identity Y
Subdirectory Enter the subdirectory to which the file set belongs gen_​text_​input Y
Name Enter the name of the file set gen_​text_​input Y
Owner Enter the owner of the path.​ The owner can be a user name or a combination of domain and user name.​ For example: admin1 or domanin1\admin1.​ Owner can be specified as 'root'.​ Changes are possible only while the file system is empty.​ gen_​text_​input Y
Group Enter an associated group for the path.​ Explicitly configure access the control list if read or write access is required for the group.​ gen_​text_​input
Comments Specify the comment that appears in the output of the "lsfset" command.​ gen_​text_​input
Type Choose a file set type.​ Independent file sets allow for snapshots and group quotas.​ Dependent file sets support quotas only at the level of file system that contains the file set.​ There are other differences between the two types for inode space, WAN caching, deletion, and linking.​ ibm​Storwize​File​Set​Sub​Type Y
Independent parent file set that dependent file set belongs to gen_​text_​input
Maximum number of inodes Enter a maximum number of inodes that the file set can use.​ This value depends on the available inodes in the file system.​ The minimum number of inodes that must be available to create a file set is 1024.​ You cannot reduce the maximum number of inodes to less than the number of allocated inodes.​ The system rounds up the value that you enter to fit into the blocks needed to accommodate the request.​ As a result, the maximum number of inodes can be higher than value that you entered.​ gen_​text_​input
Allocated number of inodes Enter a number of inodes to be allocated when the file set is created.​ Allocating inodes increases the time it takes to add file sets to system; however, all subsequent writes are faster.​ The number of maximum allowed inodes cannot be decreased below the allocated number.​ To allocate all inodes for a files set, specify 0.​ The system rounds up to fit into the blocks needed to accommodate the request.​ As a result, the maximum number of inodes can be higher than the value that you entered.​ gen_​text_​input
Set a quota Check to enable quota creation gen_​text_​input
Soft limit Enter the soft quota limit.​ At the soft quota limit, a grace period starts.​ Data can be written until the grace period expires, or until hard quota limit is reached.​ gen_​text_​input
ibm​Storwize​Quota​Soft​Hard​Limit​Units
Hard limit Enter the hard limit value.​ At the hard quota limit, additional data cannot be stored until files are removed.​ Root user allocation has no quota limits.​ gen_​text_​input
ibm​Storwize​Quota​Soft​Hard​Limit​Units
Snapshot Choose one or more snapshots to associate with the file set ibm​Storage​File​Set​Snapshot​Rule​Identity
Outputs
Output Description Type
IBM_​STORWIZE_​OUTPUT_​FILESET_​IDENTITY Output of file set identity ibm​Storwize​File​Set​Identity
IBM_​STORWIZE_​OUTPUT_​ACCOUNT_​NAME Output of infra account name account​Name
IBM_​STORWIZE_​OUTPUT_​FILESET_​NAME Output of file set name gen_​text_​input
IBM_​STORWIZE_​OUTPUT_​DATACENTER Output of datacenter name on which selected operation was performed datacenter​Name