The VIMS capacity exceeds 16 TB after capacity expansion Highlighted

80 0 1 0

Handling the Issue that the VIMS Capacity Exceeds 16 TB After Capacity Expansion.


[Keywords]


Virtual SAN, capacity expansion, 16 TB.


[Applicable Version]


FusionCompute V100R006C00 to V100R006C00SPC002


[Confidentiality]


Internal


[Description]



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.

 

[Cause]


In this version, the capacity of a virtual SAN device cannot exceed 16 TB after capacity expansion.


[Impact]


The capacity expansion fails, and the newly expanded space cannot be used to create data stores.


[Procedure]


l Scenario 1: Expansion of the original LUN capacity in the data store


Recovery method: 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   Scenario 2: Multi-LUN capacity expansion


a) 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.


b) Recovery method 2 - rerform the following steps:


1. 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.


2. 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.


3.    Edit the exported 2M.data file and modify the VIMS maptable table.


a) Run the vim -b /home/2M.data command to open the 2M.data file in binary mode.


b) Run the :%!xxd command to view the file in hexadecimal mode.


c) 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.

 

144658ux2hxkd34hkjljpj.jpg?32.jpg


d. Run the :%!xxd -r command to switch to the binary mode.


e. Run the :wq command to save the modification and exit.


4. 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.


5. 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;

 

144702hwx68adyw6yzyxny.jpg?33.jpg



6. 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

 

144705p225ysdy9h960yh5.jpg?34.jpg


7. 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';


8. Run the service vrmd restart command to restart the vrmd service.

 

144709y55a2l53ev3vkknp.png?35.png


9. Log in to the background of the host associated with the data store, update the vbs_storageunit table in the BSB database, and set the unit_type parameter of the newly expanded LUN to 0.


sqlite3 /opt/galax/data/bsb/vbsdb_bsb "update vbs_storageunit set unit_type=0 where id='scsi-id';


scsi-id indicates the SCSI ID of the newly expanded LUN.

 

144713c47k1zs0476oh17s.jpg?36.jpg


10. Run the service vnad restart command to restart the vnad service.

 

144717egqm2wjh0cjd3gj3.png?37.png


11. Log in to all hosts associated with the data store and perform steps 9 to 10 in sequence.


12. After the preceding steps are performed, the new LUN is removed from the original data store and can be added as a new data store.


  • x
  • convention:

Login and enjoy all the member benefits

Login and enjoy all the member benefits

Login