No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Oceanstor 5800 V3R1C10-the storage report write cache closed

Publication Date:  2016-06-22 Views:  57 Downloads:  0
Issue Description
Storage reported that the write cache is closed.
Alarm Information

we check the alarm in the event log:

    cid:image002.png@01D174A4.BB8243B0

Handling Process

1.1.1 Analysis on Storage

1. On the storage, there is event records show that the write cache is closed. After about 20s it’s recovered in device manager.

2. BBU3 reports power is not full at 2016-03-02 01:58:27 time point. And after 4’s charging completed and become full at 2016-03-02 01:58:31. At the same time the alarm recovered.

cid:image002.png@01D174A4.BB8243B0

Remark: 98%~100% represents power full for old version of BBU and 96%~100% for new version.

3. At the same time BBU0 is in periodic discharge test. The event shows that:

4. The discharge is triggered by system to make sure the bbus can work normally. It discharges the BBU firstly and then charges.

Discharge: The BBU0 discharge start at 00:00:01, end at 01:29:54.

cid:image001.png@01D1749E.4177CC80

cid:image003.png@01D1749E.4177CC80

The test begins at 00:00:01 and ends at 01:29:54. Here the time point in driver log is about 10s earlier than in device manager because the device manager is in upper level of system. The time point in driver log is more exactly.

Charge: The BBU0 charges starts at 01:29:54, ends at 03:32:33. Here at the issue happen time 01:58:28, the BBU0’s in charging.

cid:image004.png@01D1749F.245705C0

     

Root Cause

BBU0 is in periodic discharge test. At the same time the BBU3’s power is not full (97%, There is electric leakage for each BBU event there is no usage of them.). For 2+1 5800V3 more than 1 BBU is not full, the system closes cache.

Solution

As there is no influence for service, and the probability is extremely low (BBU vendor assess that the probability is 0.0001%). Recommend no action regard to this alarm.

Suggestions
NA

END