change file_system repair
Format
change file_system repair type=? [ file_system_id=? ] [ policy=? ] [ consistency_point=? ] [ backfs_id=? ] [ force=? ] [ init_space_info=? ] [ create_time=? ] [ controller=? ] [ repair_data_extent_type=? ] [ repair_meta_extent_type=? ]
Parameters
Parameter |
Description |
Value |
|---|---|---|
| type=? | Repair operation. | The value is "repair", "repairConfirm", "repairCancel", or "envClear", where:
|
| file_system_id=? | File system ID. | The value ranges from 0 to 65535. |
| policy=? | Repair policy. | The value is "consistency_repair" , "isolation_recovery" or "volume_extent_repair", where:
|
| consistency_point=? | Consistency point. | The value is "0", "1", "2", "3", "4", "5", "6", "7", "8" or "9", where:
|
| backfs_id=? | Backup file system ID. | The value ranges from 0 to 65535. |
| force=? | Forcible repair. | The value is "no" or "yes", where:
|
| init_space_info=? | Space initialization. | The value is "alloc_free_space", "merge_free_space", or "used_all_extent", where:
|
| create_time=? | Indicates the creating time of the file system. | The value is in the format of "year-month-day/hour:minute:second", where:
|
| controller=? | Indicates the owning controller of the file system.
NOTE:
When the value of "type" is "envClear", this parameter is not displayed. |
The value is in the format of XA or XB or XC or XD.X can be 0 to 3. |
| repair_data_extent_type=? | Indicates the selection of the method used to repair metadata on the Volume Extent layer.
NOTE:
When policy=volume_extent_repair, this parameter is displayed. |
The value is "scan_extent_tree", "scan_extent_tree_nmgr", or "scan_meta_ckg", where:
|
| repair_meta_extent_type=? | Indicates the selection of the method used to repair metadata on the Volume Extent layer.
NOTE:
When policy=volume_extent_repair, this parameter is displayed. |
The value is "scan_extent_tree", "scan_extent_tree_nmgr", or "scan_meta_ckg", where:
|
Example
-
To repair the file system whose ID is "0", repair type is repair, repair policy is consistency_repair, consistency point is "0", backup file system ID is "1", and forcible repair tag is "yes", run the following command.
developer:/>change file_system repair type=repair file_system_id=0 policy=consistency_repair backfs_id=1 consistency_point=0 force=yes controller=0A DANGER: You are about to repair the file system. When performing this operation, note the following: 1. During repairing the file system, do not perform other operations on the storage system or the file system. 2. Repairing the file system may cause file data loss and disk space leakage. Exercise caution when repairing the file system. 3. After successfully executing the change file_system repair, you must run the command of confirming the repair. 4. Cancel the repair when the command cannot be successfully executed or when faults occur on the controllers. Suggestion: Confirm that you want to repair the file system before running the command. 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. developer:/>
-
To repair the file system whose ID is "0", repair type is repair, repair policy is volume_extent_repair, create time is 2016-02-14/12:00:00, and forcible repair tag is "yes", run the following command.
developer:/>change file_system repair type=repair file_system_id=0 policy=volume_extent_repair create_time=2016-02-14/12:00:00 force=yes controller=0A DANGER: You are about to repair the file system. When performing this operation, note the following: 1. During repairing the file system, do not perform other operations on the storage system or the file system. 2. Repairing the file system may cause file data loss and disk space leakage. Exercise caution when repairing the file system. 3. After successfully executing the change file_system repair, you must run the command of confirming the repair. 4. Cancel the repair when the command cannot be successfully executed or when faults occur on the controllers. Suggestion: Confirm that you want to repair the file system before running the command. 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. developer:/>
