RAC exception caused by storage link problem_PHP tutorial

RAC exception caused by storage link problem

Yesterday, someone added me and said that they encountered a RAC problem. The environment is oracle 11.0.2.4, 2 nodes. The situation is as follows: CRSD is down and the cluster will not switch automatically. And it happened several times.
I asked this guy to provide the log.






Through the log, you can see that the CRSD service REBOOT difference between nodes 1 and 2 is only 1 second. clock; Voting file /dev/raw/raw1 cannot provide service for only 2 seconds. The CRSD of two nodes restarted at the same time. It can almost be concluded that it is not a problem with RAC itself.
Node 1: 2016-03-18 23:25:38.643:[cssd(6930)]CRS-1615:No I/O has completed after 50% of the maximum interval. Voting file /dev/raw/raw1 will be considered not functional in 99220 milliseconds
2016-03-18 23:26:58 CRSD REBOOTCRSD exiting: Could not init OCR, code: 26
Node 2: 2016-03-18 23:25:36.834:[ cssd(6590)]CRS-1615:No I/O has completed after 50% of the maximum interval. Voting file /dev/raw/raw1 will be considered not functional in 99760 milliseconds
2016-03-18 23:26 :59 CRSD REBOOTCRSD exiting: Could not init OCR, code: 26
Looking at the OS log again, the connectivity of the remote fiber port (WWN = 50:0b:34:20:0f:f4:f8:08) is lost. There must be a problem with the storage link here. Node 1Mar 18 23:26:38 xxxxr01 kernel: bfa 0000:81:00.0: Remote port (WWN = 50:0b:34:20:0f:f4:f8:08) connectivity lost for logical port (WWN = 21:00 :00:24:ff:09:a5:8a)Mar 18 23:26:38xxxxr01kernel: bfa 0000:81:00.0: Target (WWN = 50:0b:34:20:0f:f4:f8:08) lost connectivity for initiator (WWN = 21:00:00:24:ff:09:a5:8a)
Node 2Mar 18 23:26:48 xxxx02 kernel: bfa 0000:81:00.0: Remote port (WWN = 50:0b :34:20:0f:f4:f8:08) connectivity lost for logical port (WWN = 21:00:00:24:ff:09:a5:a2)Mar 18 23:26:48 xxxr02 kernel: bfa 0000: 81:00.0: Target (WWN = 50:0b:34:20:0f:f4:f8:08) connectivity lost for initiator (WWN = 21:00:00:24:ff:09:a5:a2)
Today, I chatted with this guy again and contacted the storage manufacturer to check the storage link. The storage is provided by Hongshan. This is the first time I have heard of domestic storage, which is quite an experience.
When problems occur in RAC, many times it is not the problem of RAC itself. I have encountered several cases where storage link problems caused RAC to be unable to provide services. When DBA encounters RAC anomalies, both software and hardware must be carefully checked so that the problem can be quickly located.

Please indicate when reprinting:
http://blog.chinaunix.net/uid/23284114.html