Allocate Directories on Shared File Server

Use the Allocate Directories on GPFS shared file server operation to create a new file set within the specified file system, if the file set does not already exist. A symbolic link to the file set is also created.

1. Expand the Fundamentals section of the GPFSClient operations.
2. Expand the Allocate Directories on GPFS shared file server node.
3. In the GPFS File System Information field, specify the name of an existing IBM Storage Scale file system on the IBM Storage Scale Server.
   You can use the Get Cluster Status operation to obtain a list of defined file systems. You can define a new file system by using the IBM Storage Scale Manager Attach Storage Volumes operation.
4. In the GPFS Fileset directory field, specify the name of the file set to be created. Do not include blank spaces in the name, and do not use the text string IBM Storage Scale in the name. The file set is created within the specified file system if it does not already exist.

   The file set is a directory that is created on the IBM Storage Scale file system that can be linked to by client deployments to write or share data.

   The input is in the format filesetName or filesetName/dir1/../dirn, where filesetName is required and is the name of the IBM Storage Scale file set, while dir1,..,dirn are optional and represent directories on the filesetName.

   If the input is in the format filesetName, the client links to the filesetName directory on the IBM Storage Scale shared file system.

   When the input is in the format filesetName/dir1/../dirn, the client links to the last specified directory, dirn.

   For example, the input can be in this format /filesetName/Prod/MQ, in which case the client links to /filesetName/Prod/MQ. Any data that is written by the client on the local linked directory is stored under /filesetName/Prod/MQ.

5. In the Storage Maximum limit (K, M, G) field, specify the maximum amount of data that the file set can use.
   The storage maximum limit represents the IBM Storage Scale hard quota for the file set. Data will not be able to be written to the file set when the maximum limit (hard quota) threshold is met. For more information about IBM Storage Scale quotas, see Managing GPFS quotas.

   Specify the unit in kilobytes, megabytes, or gigabytes by adding K, M, or G as a suffix (Example: 100M represents 100 megabytes. Specify the value as a positive integer with no preceding plus (+) character. Enter a 0 value for no maximum limit. Example of valid entries: 20M, 1024K, 1G, 0M.

   When a new file set is created and the storage limit is set, the following command is executed. This command sets no minimum limit (or soft quota) for the specified file set. It sets a maximum limit (hard quota) for the file set.

   su - gpfsprod -c 'sudo /usr/lpp/mmfs/bin/mmsetquota -j <Fileset  Name> -s 0M -h <Maximum Quota Size> <File System Name>

   For more information, see mmsetquota command.

   Note:

   • If the specified file set exists, the storage maximum limit that is defined here is ignored. For an existing file set, changing the maximum or minimum storage limit can be done only by using the IBM Storage Scale server administrator, by using the IBM Storage Scale server cluster administration commands.
   • By default, the file set minimum and maximum limits (or soft and hard quota) are not enforced for the root user. If you want to have the root user follow the specified limits, you need to update the IBM Storage Scale cluster to allow that. Run this command on the IBM Storage Scale client cluster where you want to enforce the quota for the root user:

     su - gpfsprod -c '/usr/lpp/mmfs/bin/mmchconfig enforceFilesetQuotaOnRoot=yes -i’

     This property applies only to the IBM Storage Scale cluster where the command is executed and affects only data that is written by the root user from this cluster. Each IBM Storage Scale client instance configures a separate IBM Storage Scale client cluster for each virtual machine. If you want to enforce the file set quota on root for other IBM Storage Scale client instances, you need to run this command on each of the IBM Storage Scale client clusters. For more information, see mmchconfig command. Before you change the IBM Storage Scale server cluster to enforce the file set quotas on the root user, make sure that this change does not affect any of the cluster scenarios. Keep in mind that if the quota is enforced for the root user, any process that is executed as a root user that would temporarily write data over the allowed threshold will now fail.

   You must manage the storage quota to ensure that the specified storage limit does not exceed the size of the file system.

6. In the Directory to link on local system field, specify a symbolic link to the file set that is created on the virtual machine file system at the location specified. The value provided must be a syntactically correct directory name starting with a forward slash character (/). For example: /myFileSetLink or /myFileSetLink/folder1/../foldern. Spaces are not allowed in the link name.
   The directory name that you specify as the value for the file set link must not exist. The server file set that you specified in the GPFS Fileset directory field is mounted to this local directory, so the local folder must not exist.
7. Click Submit.
8. Click Confirm when asked to validate your request.

Web_Application-was.11402667490454.GPFSClient: Allocate directories on shared file server: Fileset(testFSet14) has been created in File System (testFSys).