/ost-storage/disk6/c6d1 offline caused database been stopped

DB was stopped by itself after  added disks into disk group

• Problem Description:
  • DB was stopped by itself after we added disks into disk group
• DIAGNOSTIC ANALYSIS:

log /u01/app/crsusr/diag/asm/+asm/+ASM1/alert/log.xml on itqe-t5-2-1-zn1.us.oracle.com,and get :
-------------------------------------
Wed Dec 10 01:38:58 2014
ARB0 started with pid=40, OS id=25996
NOTE: assigning ARB0 to group 2/0x64767439 (DBDATAC6) with 1 parallel I/O
Wed Dec 10 01:38:59 2014
Direct NFS: Failed to set socket buffer size.wtmax=[1056768] rtmax=[1056768], errno=-1
Wed Dec 10 01:39:28 2014
NOTE: updating disk modes to 0x15 from 0x7f for disk 13 (DBDATAC6_0013) in group 2 (DBDATAC6): lflags 0x4
Wed Dec 10 01:39:29 2014
NOTE: process _b000_+asm1 (26096) initiating offline of disk 13.3593897209 (DBDATAC6_0013) with mask 0x7e in group 2 (DBDATAC6) without client assisting
Wed Dec 10 01:39:29 2014
NOTE: sending set offline flag message (2996513153) to 1 disk(s) in group 2
Wed Dec 10 01:39:29 2014
WARNING: Disk 13 (DBDATAC6_0013) in group 2 mode 0x15 is now being offlined
-------------------------------------
We can see /ost-storage/disk6/c6d1 is offline.
I checked the disk,the authorization of /ost-storage/disk6/c6d1 I/O  isn't 664.
When the database rebalance,the diskgroup will be dismounted then mounted by automatically.But the database will not be stopped if everything is OK.

• Solution:

chome 664 /ost-storage/disk6/c6d1

• • So the database is OK after we change the authorization of /ost-storage/disk6/c6d1 to be 664,then add the disk to failgroup again.No erro occurred.
  • It means that /ost-storage/disk6/c6d1 offline caused database been stopped.