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).
change file_system check
Format
change file_system check controller=? file_system_id=? type=? policy=? [ force=? ] [ chunk_id=? ]
Parameters
Parameter |
Description |
Value |
|---|---|---|
| controller=? | Indicates the owning controller of the file system. | The value is in the format of XA or XB or XC or XD. X can be 0 to 3. |
| file_system_id=? | File system ID. | The value ranges from 0 to 65535. |
| type=? | Type. | The value is "check" or "check_cancel", where:
|
| policy=? | Policy. | The value is "clear_dedup_meta", where: "clear_dedup_meta": clear dedupe meta. |
| force=? | Forcible check tag. | The value is "no" or "yes", where:
|
| chunk_id=? | Chunk ID. | The value ranges from 1 to 18446744073709551615. |
Usage Guidelines
- Before running this command, ensure that the file system ID is correct.
- Before running this command, ensure that the working controller ID of the file system is correct.
Example
-
To check the file system whose ID is "0", run the following command.
developer:/>change file_system check controller=0A file_system_id=0 type=check policy=clear_dedup_meta force=yes DANGER: You are about to check the file system. When performing this operation, note the following: 1. When checking the file system, do not perform other operations on the storage system. 2. Before executing a deduplication metadata clearing policy, disable periodic snapshot. Otherwise, data may be inconsistent. 3. The deduplication metadata clearing policy clears all deduplication metadata and causes the leakage of some disk space. This operation is irreversible. Perform this operation only when deduplication metadata is damaged. 4. The deduplication metadata clearing policy creates a snapshot. Do not delete the snapshot. Otherwise, data may be inconsistent. 5. After a deduplication metadata clearing policy is executed, do not enable periodic snapshot, delete an existing snapshot, or roll back a snapshot. Otherwise, data may be inconsistent. 6. The deduplication metadata clearing policy interrupts host I/Os. 7. The deduplication metadata clearing policy clears the statistics on space saved by deduplication and compression and affects the subsequent data deduplication ratio. 8. If a chunk ID is specified for the deduplication metadata clearing policy, ensure that the chunk ID is correct. Otherwise, data may be inconsistent. Contact R&D engineers for confirmation. Suggestion: Perform this operation based on customer requirements. Have you read danger alert message carefully?(y/n)y Are you sure you really want to perform the operation?(y/n)y Command executed successfully.
-
To check file system "0" by specifying the chunk ID, run the following command.
developer:/>change file_system check controller=0A file_system_id=0 type=check policy=clear_dedup_meta force=yes chunk_id=1024000 DANGER: You are about to check the file system. When performing this operation, note the following: 1. When checking the file system, do not perform other operations on the storage system. 2. Before executing a deduplication metadata clearing policy, disable periodic snapshot. Otherwise, data may be inconsistent. 3. The deduplication metadata clearing policy clears all deduplication metadata and causes the leakage of some disk space. This operation is irreversible. Perform this operation only when deduplication metadata is damaged. 4. The deduplication metadata clearing policy creates a snapshot. Do not delete the snapshot. Otherwise, data may be inconsistent. 5. After a deduplication metadata clearing policy is executed, do not enable periodic snapshot, delete an existing snapshot, or roll back a snapshot. Otherwise, data may be inconsistent. 6. The deduplication metadata clearing policy interrupts host I/Os. 7. The deduplication metadata clearing policy clears the statistics on space saved by deduplication and compression and affects the subsequent data deduplication ratio. 8. If a chunk ID is specified for the deduplication metadata clearing policy, ensure that the chunk ID is correct. Otherwise, data may be inconsistent. Contact R&D engineers for confirmation. Suggestion: Perform this operation based on customer requirements. Have you read danger alert message carefully?(y/n)y Are you sure you really want to perform the operation?(y/n)y Command executed successfully.
-
To cancel check the file system whose ID is "0", run the following command.
developer:/>change file_system check controller=0A file_system_id=0 type=check_cancel policy=clear_dedup_meta DANGER: You are about to check the file system. When performing this operation, note the following: 1. When checking the file system, do not perform other operations on the storage system. 2. Before executing a deduplication metadata clearing policy, disable periodic snapshot. Otherwise, data may be inconsistent. 3. The deduplication metadata clearing policy clears all deduplication metadata and causes the leakage of some disk space. This operation is irreversible. Perform this operation only when deduplication metadata is damaged. 4. The deduplication metadata clearing policy creates a snapshot. Do not delete the snapshot. Otherwise, data may be inconsistent. 5. After a deduplication metadata clearing policy is executed, do not enable periodic snapshot, delete an existing snapshot, or roll back a snapshot. Otherwise, data may be inconsistent. 6. The deduplication metadata clearing policy interrupts host I/Os. 7. The deduplication metadata clearing policy clears the statistics on space saved by deduplication and compression and affects the subsequent data deduplication ratio. 8. If a chunk ID is specified for the deduplication metadata clearing policy, ensure that the chunk ID is correct. Otherwise, data may be inconsistent. Contact R&D engineers for confirmation. Suggestion: Perform this operation based on customer requirements. Have you read danger alert message carefully?(y/n)y Are you sure you really want to perform the operation?(y/n)y Command executed successfully.
