Creating a WORM File System

Prerequisites

• The device is working correctly.
• The license file of the WORM feature is valid.
• The global security compliance clock has been initialized.

Procedure

1. Log in to DeviceManager.
2. Choose Provisioning > File System.
3. Click Create.

   The Create File System dialog box is displayed.

4. Table 2-1 describes related parameters.
   Table 2-1 File system parameters

   Parameter	Description	Value
   Name	Name of the file system.	[Value range] The name must be unique. For V500R007C00, the name can contain only letters, digits, and underscores (_). For V500R007C10 and later versions, the name can contain only letters of any language, digits, and underscores (_). The name must contain 1 to 255 characters. [Example] FileSystem001
   Description	Description of the file system.	[Example] -
   Thin Provisioning	Enables or disables thin provisioning to allow or forbid the creation of thin file systems. NOTE: If thin provisioning is enabled, the storage system dynamically allocates storage capacity to file systems based on the actual capacity used by hosts instead of allocating a preset capacity, achieving on-demand allocation.	[Example] Enabled
   Owning Storage Pool	Storage pool to which the file system you are creating belongs. NOTE: You can only choose the storage pool which is used for File Storage Service. If the storage system has no storage pool, click Create to create one.	[Example] StoragePool001
   Capacity	File system capacity. When thin provisioning is enabled, the capacity is the maximum capacity allocated to the thin file system. That is, the total capacity dynamically allocated to the file system cannot exceed the maximum capacity. When thin provisioning is disabled, the capacity will be allocated to a thick file system once and for all. The system supports the creation of block-level file systems. To create such a file system, select capacity unit Blocks. One block is equal to 512 bytes. NOTE: If you do not specify Capacity when creating a thin file system, the capacity of the created file system is 16,384 TB by default.	[Value range] Thick file system: The maximum capacity must not exceed the available capacity of the storage pool where the thick file system resides. Thin file system: The maximum capacity can exceed the available capacity of the storage pool where the thin file system resides but must fall into the range of 1 GB to 16384 TB. [Example] 100 GB
   Use all of the free capacity of the owning storage pool	If this option is selected, all free space of the owning storage pool is allocated to this file system. NOTE: If a thin file system exists in a storage pool, services of the thin file system may fail after all free capacity of the storage pool is used to create a thick file system.	[Example] Deselected
   Snapshot Space Ratio (%)	Ratio of the file system snapshot space to the file system space. Snapshot space cannot be used to store service data of the source file system. In actual service scenarios, the space consumed by file system snapshots ≥ Source file system capacity x Snapshot Space Ratio (%). To avoid a waste of storage space, it is advised to contact Huawei technical support to set this parameter to a proper value. NOTE: For details about the file system snapshot feature, see the HyperSnap feature guide for file specific to your product model and version.	[Value range] An integer ranging from 0 to 50
   Application Scenario	Application scenarios of file systems, which include: VM: After this scenario is selected, the system will set the file system block size to 8 KB, and automatically adjust system resources to adapt to this scenario. Database: In this scenario, you are advised to select a storage pool containing only SSDs for the file system and enable the data compression function. When the storage pool to which a file system belongs contains only SSDs, the system will set the file system block size to 16 KB and enable the data compression function by default. If you choose Advanced > Tuning and disable the data compression function, the system will set the file system block size to 8 KB. In this scenario, you are advised to enable the data compression function. When the storage pool to which a file system belongs contains other types of disks, the system will set the file system block size to 8 KB and disable the data compression function by default. If you choose Advanced > Tuning and enable the data compression function, the system will remain the file system block size as 8 KB. In this scenario, you are not advised to enable the data compression function. User-defined: In this scenario, you must manually specify the file system block size.	[Value range] VM, Database, or User-defined. [Example] User-defined
   File System Block Size	This parameter is displayed only when Application Scenario is set to User-defined. Data in a file system consists of blocks. The size of the blocks (also known as file system block size) affects disk space usage and performance. You are advised to configure the block size following the principles below: Select 16 KB when the size of most files in the file system is smaller than 100 KB, the data deduplication or data compression function will be enabled, or the file size and scenarios are not specified. Select 32 KB when the size of most files in the file system is between 100 KB and 1 MB. Select 64 KB when the size of most files in the file system is larger than 1 MB or the file system mainly processes bandwidth-consuming large I/Os, in scenarios such as Media & Entertainment (M&E) industry, and archive and backup of large files. NOTE: To modify this parameter after a file system is created, run the change file_system general file_system_id=? block_size=? command.	[Value range] 4 KB, 8 KB, 16 KB, 32 KB, or 64 KB. [Example] 16 KB
   Quantity	Number of file systems to be created in batches. Set this parameter based on your needs. NOTE: This option is invalid when you select Use all the free capacity of the owning storage pool. A maximum of 100 file systems can be created at one time. When multiple file systems are created, the system will automatically add suffixes to distinguish between file systems. The file systems created in a batch have the same capacity.	[Value range] 1 to 100 [Example] 5
   Manually specify the suffix	When creating multiple file systems, the system automatically adds a suffix number to the name of each file system for file system distinction. You can manually set the start suffix number after selecting this option. NOTE: If this option is not selected, the suffix number starts at 0000 by default.	[Example] -
   Start Number	This parameter is valid after Manually specify the suffix is selected. From the start number you configured, the system adds an increasing suffix number to the name of each file system to distinguish the file system.	[Value range] 0 to (10000 minus the quantity of file systems to be created) NOTE: For example, if you want to create 30 file systems, the start number is from 0 to 9970.
   Security Style	Select a security style based on service requirements. The security style defines the access control mechanism of the file system accessible through multiple protocols. Mixed Applies to the scenario in which both CIFS and NFS users can access and control the file system. Either CIFS or NFS permissions are valid. The latest configured permissions prevail. Native Applies to the scenario in which Windows NT ACLs control CIFS users' permissions and UNIX mode bits control NFS users' permissions. In this mode, Windows NT ACLs and UNIX mode bits will neither affect nor synchronize with each other. For CIFS share access, the system checks whether a Windows user has the access permission based on the Windows NT ACLs. For NFS share access, the system checks whether a UNIX user has the access permission based on the UNIX mode bits. NTFS Applies to the scenario in which Windows NT ACLs control CIFS user permissions. NOTE: In NTFS mode, you are advised to set Mapping Mode to Support only user mapping in the current system. (To set Mapping Mode, choose Provisioning > User Authentication > User Mapping > Set Mapping Parameters.) In addition, for V500R007C60SPC300 and later versions, you are advised to configure a default Windows user in the NFS service. (To configure a default Windows user, choose Settings > Storage Settings > File Storage Service > NFS Service.) The default Windows user must be an existing local authentication user or AD domain user. This parameter applies to V500R007C60 and later versions. UNIX Applies to the scenario in which UNIX mode bits, NFSv4 ACLs, or NFSv3 ACLs control NFS user permissions. NOTE: In UNIX mode, you are advised to set Mapping Mode to Support only user mapping in the current system. (To set Mapping Mode, choose Provisioning > User Authentication > User Mapping > Set Mapping Parameters.) In addition, for V500R007C60SPC300 and later versions, you are advised to configure a default UNIX user in the CIFS service. (To configure a default UNIX user, choose Settings > Storage Settings > File Storage Service > CIFS Service.) The default UNIX user must be an existing local authentication user or NIS/LDAP domain user. This parameter applies to V500R007C60 and later versions. NOTE: This parameter applies to V500R007C50 and later versions.	[Example] Mixed

5. Set the type of the file system to WORM.
   1. Click Advanced.

      The Advanced dialog box is displayed.

   2. Set the type of the file system to WORM.

      Click the WORM tab, select Enable, and set the related parameters. Table 2-2 describes the related parameters.

      Table 2-2 WORM parameters

      Parameter	Description	Value
      Mode	Regulatory compliance: For files within the Retention, common users and system administrators cannot modify, delete, or rename them. For files beyond the Retention, common users and system administrators cannot modify or rename, but can delete them. For file systems containing files within the Retention, system administrators cannot delete the file systems. For file systems containing files that are all beyond the Retention, system administrators can delete the file systems. Enterprise compliance: For files within the Retention, common users and system administrators cannot modify, delete, or rename them. For files beyond the Retention, common users and system administrators cannot modify or rename, but can delete them. For file systems with the enterprise compliance property, system administrators can delete the file systems whatever files in the file systems are within or beyond the Retention.	This parameter cannot be modified.
      Min. Retention	Minimum retention period supported by the WORM file system. The retention period of a file in the WORM file system cannot be smaller than the value of this parameter.	[Value range] 0 to 70 years or Indefinite. [Default value] 3 years [Example] 3 years NOTE: Min. Retention must be smaller than or equal to Default Retention and Max. Retention.
      Max. Retention	Maximum retention period supported by the WORM file system. The retention period of a file in the WORM file system cannot be larger than the value of this parameter.	[Value range] 1 day to 70 years or Indefinite. NOTE: The maximum retention period cannot be 0. [Default value] 70 years [Example] 10 years
      Default Retention	Default retention period supported by the WORM file system. The retention period of a file in the WORM file system is the default value of the parameter if you do not set a retention period for the file.	[Value range] If the maximum retention period ranges 1 day to 70 years, the default retention period is a value between the minimum and maximum retention periods. If the value of the maximum retention period is Indefinite, the default retention period is a value between the minimum retention period and 70 years or Indefinite. [Default value] Regulatory compliance: 70 years Enterprise compliance: 3 years [Example] 10 years NOTE: To set Default Retention as Indefinite, you must set Max. Retention to Indefinite. Otherwise, the setting fails.
      Automatic Lock	If the function is enabled and a file is not modified within the Lockout Wait Time (hours), files enter locked state automatically. Therefore, the file is under protection, and you can only read the file under locked state, but cannot modify, delete or rename it. NOTE: Write operation include file data change or metadata change.	[Default value] Enable [Example] Enable
      Lockout Wait Time (hours)	Retention of a file enters the locked state. NOTE: This parameter is valid only when Automatic Lock is enabled.	[Value range] The value is an integer ranging from 2 to 168. [Default value] 2 [Example] 10
      Automatically Delete	If this mode is enabled, the system automatically deletes files whose protection period is overdue. NOTE: Before enabling this function, ensure that files do not need protection and can be automatically deleted by the system after they expire.	[Default value] Disabled [Example] Enable

   3. Click OK.

      The Create File System dialog box is displayed.

6. Confirm the operation of creating the WORM file system.
   1. Click OK.

      The Execution Result dialog box is displayed indicating operation success.

   2. Click Close.

Follow-up Procedure

• If the automatic lock function of the WORM file system is not enabled, you must enable files in the file system to enter the protection state. If the automatic lock function is enabled for the WORM file system, you can also enable the files to enter the protection state manually within a specific period of time (Lockout Wait Time) since a change based on service requirements. For details about operations, see Setting a File to Enter the Protection State.
• If the automatic deletion function is not enabled for the WORM file system and you want to delete a file, you must manually delete it. For details about operations, see 4.1.7 Manually Deleting Expired Files from a WORM File System.