Hello all,
This case is about the host can't write the NL_SAS LUN for OceanStor 2200 V3.
【Problem Description】:
OceanStor 2200 V3 - Host can't write the NL_SAS LUN
【Problem Analysis】:
1, There is only one NL_SAS LUN, LUN ID 3, LUN Name NL-SAS_LUN01.
2, The NL_SAS LUN has used 16337338368(KB), and there are 11 snapshots with the NL_SAS LUN, the 11 snapshots have used 17739808768(KB). So the total used capacity is 32498(GB).
3, The NL_SAS storage pool almost has no free capacity. And, in the storage event, there is Critical alarm that the capacity of storage pool (name NL-SAS_Pool1, ID 2) is about to be used up.
734026 2020-02-05 11:54 0xF00D80120 Fault Critical Unrecovered None
The capacity of storage pool (name NL-SAS_Pool1, ID 2) is about to be used up. The used capacity reaches the threshold of 90%, which may cause service interruption to this storage pool. The performance may decrease, expand the capacity as soon as possible. This alarm can be cleared when (3.92TB) of capacity is added.
Step1 Check whether unused data exists in the storage pool.
1.1 If yes, delete unused data.
1.2 Expand the capacity of the storage pool.
1.3 If the HyperCDP schedule is configured, you are advised to enable the automatic deletion function of the storage pool. If the alarm persists=>[Step2].
Step2 Collect related information and contact technical support engineers.
734025 2020-02-05 11:54 0xF00D80119 Fault Major Unrecovered None
The used capacity of storage pool (name NL-SAS_Pool1, ID 2) reaches the alarm threshold (80%), total capacity (31.73TB), used capacity (31.73TB). The performance may decrease, expand the capacity as soon as possible. This alarm will be cleared with a capacity expansion of (8.43TB).
Step1 Check whether unused data exists in the storage pool.
1.1 If yes, delete unused data.
1.2 Expand the capacity of the storage pool.
1.3 If the HyperCDP schedule is configured, you are advised to enable the automatic deletion function of the storage pool. If the alarm persists=>[Step2].
Step2 Collect related information and contact technical support engineers.
【Root Cause】:
The capacity of storage pool (name NL-SAS_Pool1, ID 2) is about to be used up.
【Solution Description】:
1, Please add new NL_SAS disk to expand capacity to the NL_SAS storage pool.
2, Based on your actual situation, please delete some snapshots and modify the snapshot strategy, to decrease the snapshot number and to decrease the snapshot capacity.
This is my case. I hope it helps to you.
