Formatting volumes with data reduction enabled (only when event log KARS06201-E, KARS06220-C, KARS06221-C, or KARS06222-C is output) (Baremetal)

This section describes the procedure to be performed only when event log KARS06201-E, KARS06220-C, KARS06221-C, or KARS06222-C is output in Restoring. If none of these event logs is output, you can skip the steps in this section.

CAUTION:

The procedure in this section assumes that the operation result of chunk formatting has already been confirmed in step 3 of Verifying that restore is completed. Verify to perform the operations in the correct order.
When you start the storage cluster in maintenance mode, volumes with data reduction enabled cannot be deleted. For this reason, to delete volumes with data reduction enabled, perform the procedures described in Restore workflow before deleting the volumes.

[On the controller node] Obtain the information about the storage controller corresponding to Storage controller ID indicated in event log KARS06201-E, KARS06220-C, KARS06221-C, or KARS06222-C.
CLI: storage_controller_show

The required parameter is as follows:
- --id <Storage-controller-ID-indicated-in-event-log-KARS06201-E-or-KARS06220-C-or-KARS06221-C-or-KARS06222-C>
[On the controller node] Obtain the information about the storage node corresponding to activeStorageNodeId in storage controller information.
CLI: storage_node_show

The required parameter is as follows:
- --id <activeStorageNodeId-obtained-in-step-1>
[On the controller node] Confirm the IP address (IPv4) of the control port from storage node information.

Confirm the control port IP addresses (IPv4) for all the storage nodes corresponding to Storage controller ID indicated in event log KARS06201-E, KARS06220-C, KARS06221-C, or KARS06222-C.
[On the controller node] Make an SSH connection to the storage nodes confirmed in step 3.
```
$ ssh -i <passphrase-of-private-key> -o UserKnownHostsFile=/dev/null \
-o StrictHostKeyChecking=no \
hitachi_rescue_person@<IP-address-of-control-port>
```
Note:
- The target private key files are the ones that you obtained in step 4 of Collecting information required for restore and that do not include ".pub" in their file names. When you created the key files as shown in the execution example of step 4, key files sample_ed25519 and sample_ed25519.pub exist, and sample_ed25519 serves as a private key file.
- For the procedure described in subsequent step 5 ([On the storage node]), you need to perform operation for each storage node confirmed in step 2. By making an SSH connection with multiple storage nodes simultaneously, you can perform operations with those nodes in parallel.
[On the storage node] Run the script for formatting volumes with data reduction enabled.
```
$ sudo /usr/local/bin/format_volumes.sh
```
Note:
- The approximate required time for running the script is as follows:
  
  Number of volumes corresponding to Storage controller ID × 30 seconds
  
  The number of volumes corresponding to Storage controller ID is the number of volumes output by running the CLI command volume_list --storage_controller_id <str>.
- Volumes with data reduction enabled are formatted asynchronously by running the script. The time until formatting completes varies according to the number of volumes with data reduction enabled and their capacity.
  
  The estimated time (in seconds) until formatting completes can be calculated as follows:
  
  You can confirm the volumes whose status is MetaDataConsistencyError by the CLI command volume_list.
  
  ∑ (60 [seconds] + (size of volumes whose status is MetaDataConsistencyError [byte] / 512 [byte/s]) × 280 [byte] / (1024 × 1024 × 1024) [byte])
  
  Example:
  
  When there is one 100-GiB volume and one 10-GiB volume whose status is MetaDataConsistencyError
  
  (60 + ((100 × 1024 × 1024 × 1024) / 512) × 280 / (1024 × 1024 × 1024)) + (60 + ((10 × 1024 × 1024 × 1024) / 512) × 280 / (1024 × 1024 × 1024)) ≒ 180 seconds
[On the controller node] Verify whether volumes whose status is MetaDataConsistencyError remain.
CLI: volume_list

The required parameter is as follows:
- --saving_setting Compression
If volumes whose status is MetaDataConsistencyError remain even after formatting volumes of all the storage nodes corresponding to Storage controller ID indicated in event log KARS06201-E, KARS06220-C, KARS06221-C, or KARS06222-C, contact the Hitachi design team.
After verifying the volume status in step 6, return to Verifying that restore is completed, and then perform step 5 and subsequent steps.