This post is is related to the issue that the VIMS capacity exceeds 16 TB after capacity expansion. Please read further down in order to find the solution to it.
Diagnostic
The total capacity of a virtual SAN device exceeds 16 TB after capacity expansion, and the capacity expansion fails. The number of storage devices in the data store is displayed as 2, but the capacity of the data store does not increase.
Troubleshooting
Upgrade the system to V100R006C00SPC003 or later. After the upgrade is complete, the platform automatically performs capacity expansion, and the capacity expansion is successful.
l Recovery method 1: Upgrade the system to V100R006C00SPC003 or later. After the upgrade is complete, the platform automatically performs capacity expansion, and the capacity expansion is successful.
l Recovery method 2: Perform the following steps:
a) If alarm Faulty Data Store on the Host is displayed, clear the alarm based on the FusionSphere product documentation and then perform the subsequent steps.
b) Obtain the SCSI ID of the data store that fails to be expanded, log in to one of the hosts associated with the data store, and export the first 2 MB data of the SCSI device.
dd if=/dev/disk/by-id/scsi-id of=/home/2M.data bs=1M count=2 iflag=direct
scsi-id indicates the SCSI ID of the first storage device in the data store.
c) Edit the exported 2M.data file and modify the VIMS maptable table.
I. Run the vim -b /home/2M.data command to open the 2M.data file in binary mode.
II. Run the :%!xxd command to view the file in hexadecimal mode.
III. Enter i to enter the editing mode, locate the rows containing 3000 and 7b10 and change the values at the corresponding positions to 01 and 00, as shown in the following figure. Press Esc to exit the editing mode.
IV. Run the :%!xxd -r command to switch to the binary mode.
V. Run the :wq command to save the modification and exit.
d) Roll back the modified data to the SCSI device.
dd if=/home/2M.data of=dev/disk/by-id/scsi-id bs=1M count=2 oflag=direct
scsi-id indicates the SCSI ID of the first storage device in the data store.
e) Log in to the VRM database and query the data store. Two storage devices are displayed in the su_list column and separated by commas (,).
Select * from tbl_vs_datastore where ds_index=ds_id;
f) Update tbl_vs_datastore and delete the second storage device displayed for su_list.
update tbl_vs_datastore set su_1ist='CBABOO5F1A23475BBF17CD56D43O3565' where ds_index=ds_id;" before reading stdin" before reading stdin
g) Update the tbl_vs_storage_unit table and set the ds_index parameter of the newly expanded LUN to null.
update tb1_vs_storage_unit set ds_index=null where su_id='6BFBF63CCK224BDD9962O841OB678EF1';
Run the service vrmd restart command to restart the VRMD service.
