Basic Information:
Item | Description |
Storage type | Distributed storage |
Product version | OceanStor 100D 8.0.3; OceanStor Pacific series 8.1.0; OceanStor Atlantic series 8.1.0 |
Problem type | Parts replacement |
Keyword | Alarms and events; Alarm reporting failures; Details |
Symptom:
After the storage system generates an alarm and the alarm is handled, the alarm is not cleared on DeviceManager. Alternatively, the storage system is faulty but no alarm is generated on DeviceManager.
Diagnosis:
Check whether the 0x1EA650002 alarm is generated on DeviceManager.
Log in to the faulty node and run the df -h command to check whether the space usage of the partition where /opt is located reaches 100%.
Cause:
After the storage system runs for a long time, the space usage of the partition where /opt is located may reach 100%. As a result, the fma component of the corresponding node cannot write alarms to /opt/dfv/oam/fma/data/alarm.dat. Therefore, the node cannot report alarms to management nodes.
Solution:
Log in to DeviceManager.
Choose Monitor > Alarms and Events.
Check whether the 0x1EA650002 alarm exists in the Alarms tab page.
If yes, go to 4.
If no, contact technical support engineers.
Click the information in the Description column to view the alarm details. In Description on the Alarm Details page, obtain the IP address of the node for which the alarm is generated and check whether the directory mounted to the node is /opt or the root directory, as shown in Figure Alarm details about insufficient disk partition space.
Figure1 Alarm details about insufficient disk partition space
If yes, check whether Use% is 100%.
If Use% is 100%, go to 5. If Use% is not 100%, contact technical support engineers.
If no, check whether Use% of / under Mounted on is 100%. If Use% is 100%, go to 5. If Use% is not 100%, contact technical support engineers.
If yes, go to 5.
If no, contact technical support engineers.
If the mounted directory is /opt, log in to the faulty node as user dsware, switch to user root, and run the df -h command to check whether Use% is 100%.
[root@FSM1~]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 29G 56M 29G 1% /dev tmpfs 29G 100K 29G 1% /dev/shm tmpfs 29G 1.6G 27G 6% /run tmpfs 29G 0 29G 0% /sys/fs/cgroup /dev/vda4 35G 12G 21G 36% / tmpfs 29G 1.5M 29G 1% /tmp /dev/vda2 976M 123M 786M 14% /boot /dev/vda1 200M 6.3M 194M 4% /boot/efi tmpfs 5.7G 0 5.7G 0% /run/user/0 tmpfs 512M 36K 512M 1% /OSM/data/omm/perf
If the mounted directory is the root directory, log in to the faulty node as user dsware, switch to user root, and run the df -h command to check whether the /opt partition exists in Mounted on.
Run the rm command to clear unnecessary files from the disk partition where /opt is located under the guidance of technical support engineers.
On DeviceManager, check whether Status is Auto recovered on the Alarm Details page, as shown in Figure Details about the recovered alarm.
Figure1 Details about the recovered alarm
If yes, rectify the fault as instructed in this section.
If no, contact technical support engineers.
