The chunk service manages the physical disks (except system disks) on each node. It formats the data partitions on the physical disks, mounts them to chunks, and controls the partitions through those chunks.
Procedure
Run the following command on a cluster node to view its data partition information:
zbs-chunk [--ins_id <id>] partition list
| Parameter | Description |
|---|---|
--ins_id <id> | Optional. The physical disk pool ID. This parameter can be used to filter and display information for a specific physical disk pool in environments with multiple physical disk pools. |
Output example
============== ============================================================== ==================================== ============ =========== ===================== =============== ================= ========== ============= ==================================== =========== =================
PATH DEVICE ID UUID TOTAL SIZE USED SIZE NUM CHECKSUM ERRORS NUM IO ERRORS STATUS ERRFLAGS NUM SLOW IO PART UUID WARNFLAGS CHECKSUM ENABLE
============== ============================================================== ==================================== ============ =========== ===================== =============== ================= ========== ============= ==================================== =========== =================
/dev/nvme2n1p1 nvme-eui.01000000000000005cd2e40e40575551-part1 b7a5b3bc-cd9b-483a-8496-b9984dd0f361 1.46 TiB 1.18 TiB 0 0 PARTITION_MOUNTED 0 0 f8141e82-17e4-4b7e-8c25-85c14fa319b6 0 0
============== ============================================================== ==================================== ============ =========== ===================== =============== ================= ========== ============= ==================================== =========== =================Output note
| Parameter | Description |
|---|---|
INS ID | The physical disk pool ID (displayed only if there are multiple physical disk pools and no filter is applied). |
PATH | The partition path. |
DEVICE ID | The physical disk ID. |
UUID | The unique UUID identifier of the data partition. |
TOTAL SIZE | The total capacity of the data partition. |
USED SIZE | The used space. |
NUM CHECKSUM ERRORS | The number of checksum errors. |
NUM IO ERRORS | The number of I/O errors. |
STATUS | The partition status. |
ERRFLAGS | The error flags. |
NUM SLOW IO | The number of slow I/Os. |
PART UUID | The unique UUID identifier of the physical partition. |
WARNFLAGS | The alarm flags. |
CHECKSUM ENABLE | Whether checksum is enabled: 0 = disabled, 1 = enabled. |
Procedure
Format the data partition under a specified path
Run the following command on a cluster node to format the data partition under the specified path:
zbs-chunk [--ins_id <id>] partition format <path>
Format the data partition with existing data under a specified path
Run the following command on a cluster node to format the data partition with existing data under the specified path:
zbs-chunk [--ins_id <id>] partition format --force <path>
Note:
Running this command will erase all existing data on the data partition. Proceed with caution.
Format the data partition for all-flash SSD usage
Run the following command on a cluster node to format the data partition with existing data under the specified path:
zbs-chunk [--ins_id <id>] partition format --ignore_data_checksum <path>
Information:
In environments with multiple physical disk pools, if the specified partition is mounted by another physical disk pool, the command will fail. In this case, you must unmount the corresponding partition before running the command.
| Parameter | Description |
|---|---|
--ins_id <id> | Optional (required in a multi-physical disk pool environment). The physical disk pool ID. This parameter specifies the physical disk pool used for formatting in a multi-physical disk pool environment. |
Output example
Partition successfully formattedProcedure
Mount the empty data partition
Run the following command on a cluster node to mount a data partition to the specified path:
zbs-chunk [--ins_id <id>] partition mount <path>
Mount the data partition with existing data
Note:
Mounting data partitions with existing data is a risky operation. Proceed with caution when using the following commands.
Run the following command on a cluster node to mount the data partition with existing data to the specified path:
zbs-chunk [--ins_id <id>] partition mount --force <path>
| Parameter | Description |
|---|---|
--ins_id <id> | Optional (required in a multi-physical disk pool environment). The physical disk pool ID. This parameter specifies the physical disk pool used for mounting in a multi-physical disk pool environment. It must be consistent with the physical disk pool used for formatting. |
Output example
Partition successfully mountedProcedure
Run the following command on a cluster node to unmount the data partition under the specified path from the chunk:
zbs-chunk partition umount <path>
Output example
Partition is STAGING, umount will be done in backgroundProcedure
Run the following command on a cluster node to stop unmounting the data partition under the specified path from the chunk:
zbs-chunk partition cancel-umount <path>
Output example
Partition cancel umount submittedProcedure
Run the following command on a cluster node to unmount the data partition under the specified path from the chunk. This operation cannot be undone:
zbs-chunk partition umount --scheme uuid --mode offline <uuid>
Output example
Partition is STAGING, umount will be done in backgroundProcedure
Run the following command on a cluster node to set the data partition under the specified path to a healthy status:
zbs-chunk partition set-healthy <path>
Output example
Partition is set healthy!Procedure
Run the following command on a cluster node to set the data partition under the specified path to an unhealthy status:
zbs-chunk partition set-unhealthy <path>
Output example
Partition is set unhealthy! umount and recover will be done in backgroundProcedure
Run the following command on a cluster node to isolate sub-healthy data partitions in the specified path:
zbs-chunk partition isolate <path>
Output example
Partition is HIGH_LAT, isolate will be done in background