No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Basic Storage Service Configuration Guide for File

OceanStor V3 Series V300R006

This document is applicable to OceanStor 2200 V3, 2600 V3, 5300 V3, 5500 V3, 5600 V3, 5800 V3, 6800 V3, 18500 V3, and 18800 V3. It describes the basic storage services and explains how to configure and manage them.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Creating a File System

Creating a File System

This section describes how to create file systems. File systems can share storage resources in the form of directories.

Prerequisites

  • A storage pool has been created for the file storage service.
  • You are an administrator or super administrator.
  • For 18000 series storage systems, the file system service for a controller enclosure has been enabled.

Context

The long file name function is available in V300R006C50 and later to control whether a file system supports long file names (255 bytes < a long file name ≤ 1023 bytes). By default, the long file name function is enabled for a new file system. Once the long file name function is enabled, you cannot disable it.

NOTE:
  • To query whether the long file name function is enabled for a file system, run the show file_system general file_system_id=? command. For more details about the command, see the command reference corresponding to your product model.
  • To create a file system that does not support long file names, run the create file_system general name=? pool_id=? long_filename_enabled=no command.
  • To enable the long file name function for a file system, run the change file_system general file_system_id=? long_filename_enabled=yes command.
  • If a file system is paired with another file system, you cannot modify its long file name settings.
  • If you upgrade a storage system to V300R006C50 or later, the long file name function is disabled by default for existing file systems.

Precautions

Services may be interrupted when all of the following conditions are met:

  • A storage pool has thin file systems.
  • The capacity of all file systems exceeds that of the storage pool.
  • The capacity of the storage pool is used up.

Procedure

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

    The Create File System dialog box is displayed.

    NOTE:

    GUIs may vary with product versions and models. The actual GUIs prevail.

  4. Set parameters for a file system.

    Table 3-8 describes the related file system parameters.

    Table 3-8 File system parameters

    Parameter

    Description

    Value

    Name

    Name of the file system.

    [Value range]

    • The name must be unique.
    • For V300R006C00 and V300R006C10, the name can contain only letters, digits, and underscores (_).
    • For V300R006C20 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 does 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 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]

    Disable

    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 addition, in actual service scenarios, the space consumed by file system snapshots is greater than or equal to the product of the source file system capacity and 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: You are advised to use full-SSDs for storage pools to which file systems belong and enable the data compression function.
      • When the storage pool to which a file system belongs uses full-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 does not use full-SSDs, 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

    If Application Scenario is set to User-defined, this parameter must be specified.

    Data in a file system consists of fixed-length 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).

    [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 Mode

    Select a security mode based on service requirements. The security mode 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.
    NOTE:

    This parameter applies to V300R006C60 and later versions.

    [Value range]

    The value can be Mixed or Native.

    [Example]

    Mixed

  5. Optional: Set a timing snapshot policy.

    1. Click Timing Snapshot Policy.

      The Timing Snapshot Policy dialog box is displayed.

    2. Set a timing snapshot policy.
      • Set the Max. Number of Timing Snapshots. The value ranges from 1 to 2048.
        NOTE:
        • When the number of created snapshots reaches the upper limit, the system automatically deletes the oldest snapshots.The total number of retained snapshots specified in all snapshot policies cannot exceed the upper limit.
        • This parameter applies to V300R006C50 and later versions.
      • Select Hours and Minute to execute the timing snapshot. The calculation begins from 00:00 every day. For example, if Every 6 Hours 10 Minute is specified, then timing snapshot will be executed at 06:10, 12:20, and 18:30 every day.

        Set the Number of Retained Snapshots. The value ranges from 1 to 2048.

        NOTE:

        Number of Retained Snapshots applies to V300R006C50 and later versions.

      • Select Daily and set Hours and the execution start time. For example, if Hours: 01:00 and 17:00 are specified, and Minute: 1 is specified, the timing snapshot will be executed at 01:01 and 17:01 every day.

        Set the Number of Retained Snapshots. The value ranges from 1 to 2048.

      • Select Weekly and set Week and the execution start time. For example, if Week: Wed, and Time: 11:50 are specified, the timing snapshot will be executed at 11:50 on Wednesday every week.

        Set the Number of Retained Snapshots. The value ranges from 1 to 2048.

      • Select Monthly and set Date and the execution start time. For example, if Date: 2 and 30 are specified, and Time: 12:10 is specified, the timing snapshot will be executed at 12:10 on the 2nd and 30th of every month.

        Set the Number of Retained Snapshots. The value ranges from 1 to 2048.

    3. Click OK.

  6. Optional: Modify advanced properties of the file system.

    1. Click Advanced.

      The Advanced dialog box is displayed.

    2. Set advanced properties of the file system.

      Click the Properties, Tuning, and WORM tabs and set related parameters.

      NOTE:
      • GUIs may vary with product versions and models. The actual GUIs prevail.
      • Before creating a WORM file system, you must run the change system secure_compliance_clock date=? command to initialize the WORM regulatory clock. For more information about WORM file systems, see the WORM Feature Guide.
      Table 3-9 Property parameters

      Parameter

      Description

      Value

      Owning Controller

      Controller to which the file system belongs.

      NOTE:

      To allocate file systems to controllers for load balancing, you are advised to select Auto select.

      [Value range]

      Based on actual conditions of available controllers of the storage system.

      [Example]

      Auto select

      [Default]

      Auto select

      Capacity Alarm Threshold (%)

      Alarm threshold of the file system capacity.

      [Value range]

      An integer ranging from 50 to 95.

      [Example]

      90

      [Default]

      90

      SSD Capacity Upper Limit of User Data

      SSD capacity upper limit of user data.

      NOTE:
      • The storage pool where the file system is created must contain SSDs and other storage media.
      • When the capacity of other storage media in the storage pool is used up, the SSD capacity used by user data may exceed the specified upper limit.
      • If the SSD capacity upper limit of user data is greater than the file system capacity after file system capacity reduction, the SSD capacity used by user data will not exceed the total file system capacity.
      • This parameter applies to V300R006C30 and later versions.

      [Value range]

      • The SSD capacity upper limit of user data cannot be smaller than 1 GB.
      • The SSD capacity upper limit of user data cannot exceed the capacity of the file system.

      Initial Capacity Allocation Policy

      Policy for a storage tier to allocate capacity to a file system.

      • Automatic allocation: The storage system automatically allocates capacity to a file system based on the ratio of the available capacity of the performance tier to that of the capacity tier. Capacity is allocated from the high-performance tier only when the capacity of the performance tier and capacity tier is insufficient.
      • Allocate from the high performance tier first: The storage system allocates capacity to a file system from the high-performance tier first. If the capacity of the high-performance tier is insufficient, the storage system allocates capacity from other storage tiers, first from the performance tier and then from the capacity tier.
      • Allocate from the performance tier first: The storage system allocates capacity to a file system from the performance tier first. If the capacity of the performance tier is insufficient, the storage system allocates capacity from other storage tiers, first from the capacity tier and then from the high-performance tier.
      • Allocate from the capacity tier first: The storage system allocates capacity to a file system from the capacity tier first. If the capacity of the capacity tier is insufficient, the storage system allocates capacity from other storage tiers, first from the performance tier and then from the high-performance tier.

      [Value range]

      Automatic allocation, Allocate from the high performance tier first, Allocate from the performance tier first, or Allocate from the capacity tier first.

      [Example]

      Automatic allocation

      [Default]

      Automatic allocation

      Snapshot Directory Visibility

      Specifies whether snapshot directories are visible.

      [Value range]

      Visible or Invisible.

      [Example]

      Visible

      [Default]

      Visible

      Max. Number of Timing Snapshots

      Maximum number of file system timing snapshots. When the number of created snapshots reaches the upper limit, the system automatically deletes the earliest timing snapshots.

      [Value range]

      An integer ranging from 1 to 2048.

      [Example]

      16

      [Default]

      16

      Delete Obsolete Read-Only Snapshots

      Enables or disables Delete Obsolete Read-Only Snapshots.

      If Delete Obsolete Read-Only Snapshot is enabled, the storage system automatically deletes the earliest read-only snapshots when both the following conditions are met:

      • The file system's used space reaches the alarm threshold.
      • The space used by snapshots is larger than the snapshot reservation space, that is, source file system capacity x Snapshot Space Ratio (%).

      [Example]

      Enable

      [Default]

      Disable

      Checksum

      Enables or disables Checksum. This function is used to check data integrity. After it is enabled, checksum will be automatically calculated when data is being written, ensuring integrity of the data to be accessed.

      NOTE:

      Enabling Checksum will impair the system performance.

      [Example]

      Enable

      [Default]

      Enable

      Automatic Update of Atime

      Enables or disables Automatic Update of Atime. Atime indicates the time when file systems are accessed. After this function is enabled, Atime will be updated every time data on file systems is accessed.

      NOTE:

      Enabling Automatic Update of Atime will impair the system performance.

      [Example]

      Enable

      [Default]

      Disable

      ADS

      Allows a file to have multiple flows to store a large amount of non-critical information. To ensure data integrity, this function is enabled by default and cannot be disabled after the file system has been created.

      NOTE:

      This parameter applies to V300R006C30 and later versions.

      [Example]

      Enable

      [Default]

      Enable

      Capacity Autonegotiation Policy

      A storage system supports the following capacity autonegotiation policies:

      • Not Use Capacity Autonegotiation: The storage capacity used by a file system is fixed and is not flexibly adjusted by the storage system.
      • Auto Expand Capacity: The storage system automatically increases file system capacity to meet users' requirements in data write when the percentage of a file system's used capacity to its total capacity reaches Auto Expand Trigger Threshold (%) and the storage pool has available space.
      • Auto Reduce or Expand Capacity: The storage system automatically adjusts the file system capacity based on file system space usage. When the percentage of a file system's used capacity to its total capacity reaches Auto Expand Trigger Threshold (%) and the storage pool has available space, the storage system automatically increases file system capacity. When the percentage of a file system's used capacity to its total capacity is smaller than Auto Reduce Trigger Threshold (%), the storage system automatically reduces the file system capacity and reclaims released storage space into the storage pool for other file systems' data writes.
        NOTE:

        Parameters related to Capacity Autonegotiation are only supported in V300R006C10 and later versions.

      [Example]

      Auto Expand Capacity

      [Default]

      Not Use Capacity Autonegotiation

      Capacity Reclamation Mode

      A storage system supports the following capacity reclamation modes:

      • Preferentially Expand Capacity: Expands the capacity to increase the file system capacity.
      • Preferentially Delete Old Snapshot: Deletes old snapshots to reclaim space for increasing the file system capacity. If HyperReplication and HyperMetro are configured for storage systems, the capacity autonegotiation policy of the primary storage system will be synchronized to the secondary storage system. If the primary storage system uses Preferentially Delete Old Snapshot, ensure that Delete Obsolete Read-Only Snapshots is enabled for the secondary storage system.

      [Example]

      Preferentially Expand Capacity

      [Default]

      Preferentially Expand Capacity

      Auto Adjust Capacity

      After you select Auto Adjust Capacity, the automatic capacity expansion or reduction policy for a file system will take effect during the service running.

      [Example]

      Enable

      [Default]

      Enable

      Auto Expand Trigger Threshold (%)

      When the percentage of the file system's used capacity to its total capacity is greater than the value of this parameter, the storage system automatically triggers file system capacity expansion.

      [Value range]

      An integer ranging from 2 to 99.

      NOTE:

      The value of Auto Expand Trigger Threshold (%) must be greater than that of Auto Reduce Trigger Threshold (%).

      [Example]

      85

      [Default]

      85

      Auto Reduce Trigger Threshold (%)

      When the percentage of the file system's used capacity to its total capacity is smaller than the value of this parameter, the storage system automatically triggers file system space reclamation and reduces file system capacity.

      [Value range]

      An integer ranging from 1 to 99.

      [Example]

      50

      [Default]

      50

      Auto Expand Upper Limit

      Upper limit for automatic expansion.

      [Value range]

      File system capacity to 16 PB

      [Example]

      120 GB

      [Default]

      File system capacity * 120%

      Auto Reduce Lower Limit

      Lower limit for automatic reduction.

      [Value range]

      1 GB to Auto Expand Upper Limit

      [Example]

      100 GB

      [Default]

      File system capacity

      Auto Expanded/Reduced Capacity Each Time

      Auto expanded or reduced capacity each time.

      [Value range]

      64 MB to 100 GB

      [Example]

      1 GB

      [Default]

      1 GB

      Table 3-10 Tuning parameters

      Parameter

      Description

      Value

      Priority Control

      Specifies the SmartQoS priority control policy.

      NOTE:

      The SmartQoS feature requires a license.

      [Value range]

      Low, Medium, or High.

      [Example]

      Low

      [Default]

      Low

      Traffic Control

      Specifies the SmartQoS traffic control policy.

      NOTE:

      The SmartQoS feature requires a license.

      If no traffic control policy exists, click Create to create one. For details, see "Creating a Traffic Control Policy" in the SmartQoS feature guide.

      [Default]

      -

      Enable deduplication

      Enables SmartDedupe. SmartDedupe deduplicates data, saving storage space.

      NOTE:

      The SmartDedupe feature requires a license.

      [Example]

      Enable deduplication

      Enable data compression

      Enables SmartCompression. SmartDedupe compresses data, saving storage space.

      NOTE:

      The SmartCompression feature requires a license.

      [Example]

      Enable data compression

      SmartPartition

      Specifies SmartPartition for the file system. SmartPartition allocates cache resources to the file system to meet the cache hit ratio required by different applications.

      NOTE:
      • The SmartPartition feature requires a license.
      • Select the owning controller of the file system manually. The controller must be the same as the owning controller of SmartPartition. Otherwise, SmartPartition is unavailable.

      If no SmartPartition exists, click Create to create one. For details, see "Creating a SmartPartition" in the SmartPartition feature guide.

      [Default]

      -

      SmartCache Partition

      Specifies SmartCache partitions for the file system. In the scenario that reads are more than writes and hot data exists, SmartCache uses SSDs as cache to improve the system read performance.

      NOTE:
      • The SmartCache feature requires a license.
      • Select the owning controller of the file system manually. This controller must be the same as the owning controller of the SmartCache partition. Otherwise, SmartCache is unavailable.
      • SmartCache does not support self-encrypting SSDs.

      If no SmartCache partition exists, click Create to create one. For details, see "Creating a SmartCache Partition" in the SmartCache feature guide.

      [Default]

      -

    1. Click OK.

      The Create File System dialog box is displayed.

  7. Click OK.

    The Execution Result dialog box is displayed, indicating that the operation succeeded.

  8. Click Close.
Translation
Download
Updated: 2019-07-12

Document ID: EDOC1000138856

Views: 61939

Downloads: 828

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next