在《Pro Oracle Database 11g RAC on Linux》书中简短提到一句：
If the disk error is transient, and the failed disk can be brought online again within a time threshold, the Fast Mirror Resync feature can help speed up the resynchronization operation. The requirement is to have a disk group with COMPATIBLE.RDBMS set to ≥ 11.1, and optionally a DISK_REPAIR_TIME. A so-called Staleness Registry keeps track of changes to the AUs within the offline disk. When the disk is brought online again, the Staleness Registry is used to recover the contents of the disk.
这里提到了fast mirror resync的Staleness Registry
事实上我看到这句的时候并不知道该怎么验证。Staleness Registry是关键字，我想，按照ASM的理念“一切都是文件”，是不是会存在文件号来标识这个东西呢。
于是我loop+kfed去读1号文件（file directory）的前256个块。这句很重要。而且你如果想复现的话，你必须保证你的磁盘组是normal或者high冗余，并且要手工触发一次某个磁盘的offline，你才能看到12和254文件，不然是空的。所有读到kfffde[0].xptr.au不是4294967295的AU都拿出来，再用kfed读一遍。（这个工作量很大加上我又不会写程序）。我的环境是AU10是1号文件，遍历下来，会发现type 20和21是KFBTYP_SR和KFBTYP_STALEDIR，SR就是staleness registry的缩写，其实到这里就卡住了，于是google搜了一下这两个文件。结果很显然会指向：
http://asmsupportguy.blogspot.com/2012/01/asm-files-number-12-and-254.html
ASM Support Guy
发现这是个大神，感觉之前的kfed都白折腾了。。。不开心。
他说ASM元数据的12和254号文件是用来实现ASM Fast Mirror Resync的。这。。。我这。。。我还继续写吗。。。
既然是12号和254号文件，就把他们搞出来看看是啥。两种方法，一种是kfed去读1号文件的12和254号块，来定位是哪个磁盘的哪个AU，另外一种是查询x$kffxp这个内存视图。本次用这个视图。
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
SELECT x.xnum_kffxp "Extent", x.au_kffxp "AU", x.disk_kffxp "Disk #", d.name "Disk name" FROM x$kffxp x, v$asm_disk_stat d WHERE x.group_kffxp=d.group_number and x.disk_kffxp=d.disk_number and x.group_kffxp=1 and x.number_kffxp =254 ORDER BY 1, 2; SELECT x.xnum_kffxp "Extent", x.au_kffxp "AU", x.disk_kffxp "Disk #", d.name "Disk name" FROM x$kffxp x, v$asm_disk_stat d WHERE x.group_kffxp=d.group_number and x.disk_kffxp=d.disk_number and x.group_kffxp=1 and x.number_kffxp =12 ORDER BY 1, 2; |
得到的结果如下：
12号文件：
|
1 2 3 4 5 6 |
Extent AU Disk # Disk name ---------- ---------- ---------- ------------------------------------------------------------------------------------------ 0 9 0 DATA_0000 350 3 DATA_0003 354 5 DATA_0005 |
254号文件：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 |
Extent AU Disk # Disk name ---------- ---------- ---------- ------------------------------------------------------------------------------------------ 0 13 1 DATA_0001 13 2 DATA_0002 348 5 DATA_0005 1 342 4 DATA_0004 344 3 DATA_0003 346 5 DATA_0005 2 12 5 DATA_0005 14 0 DATA_0000 14 2 DATA_0002 3 14 1 DATA_0001 15 0 DATA_0000 343 3 DATA_0003 4 14 5 DATA_0005 14 3 DATA_0003 341 4 DATA_0004 5 15 1 DATA_0001 16 0 DATA_0000 340 4 DATA_0004 6 15 2 DATA_0002 16 5 DATA_0005 17 0 DATA_0000 7 16 2 DATA_0002 17 3 DATA_0003 18 0 DATA_0000 8 17 2 DATA_0002 342 3 DATA_0003 344 5 DATA_0005 9 19 0 DATA_0000 338 4 DATA_0004 341 3 DATA_0003 10 16 1 DATA_0001 335 4 DATA_0004 343 5 DATA_0005 11 16 4 DATA_0004 18 2 DATA_0002 340 5 DATA_0005 12 17 1 DATA_0001 339 5 DATA_0005 339 3 DATA_0003 39 rows selected. |
获取磁盘名和真实路径对应关系
|
1 2 3 4 5 6 7 8 9 10 11 12 |
SQL> / NAME PATH -------------------- -------------------- OCR_0000 /dev/mapper/ocr01 DATA_0002 /dev/mapper/data03 DATA_0000 /dev/mapper/data01 DATA_0001 /dev/mapper/data02 DATA_0003 /dev/mapper/data04 DATA_0004 /dev/mapper/data05 DATA_0005 /dev/mapper/data06 |
所以，我们要用kfed读的12号文件是，/dev/mapper/data01的AU9。要读的254号文件有0到12共13个AU。我的AU是4M，那就是52M。有点大啊这个元数据。
为了看到实际写的数据是什么，我手工offline掉一个磁盘，让fast mirror resync开始工作，然后关掉Grid，开始读这些元数据看看能不能看懂是啥。。。
|
1 2 3 4 5 |
SQL> alter diskgroup data offline disk data_0005; Diskgroup altered. SQL> |
日志如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
2019-06-25T22:44:15.080491+08:00 SQL> alter diskgroup data offline disk data_0005 2019-06-25T22:44:15.081593+08:00 NOTE: DRTimer CD Create: for disk group 1 disks: 5 NOTE: process _user4172_+asm (4172) initiating offline of disk 5.4042301359 (DATA_0005) with mask 0x7e in group 1 (DATA) without client assisting NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0xf0f09faf, mask = 0x6a, op = clear mandatory 2019-06-25T22:44:15.086407+08:00 GMON updating disk modes for group 1 at 19 for pid 25, osid 4172 2019-06-25T22:44:15.098923+08:00 NOTE: PST update grp = 1 completed successfully NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0xf0f09faf, mask = 0x7e, op = clear mandatory 2019-06-25T22:44:15.099909+08:00 GMON updating disk modes for group 1 at 20 for pid 25, osid 4172 2019-06-25T22:44:15.109279+08:00 NOTE: cache closing disk 5 of grp 1: DATA_0005 2019-06-25T22:44:15.115767+08:00 NOTE: cache closing disk 5 of grp 1: (not open) DATA_0005 2019-06-25T22:44:15.116583+08:00 NOTE: PST update grp = 1 completed successfully NOTE: DRTimer CD Destroy: for diskgroup 1 2019-06-25T22:44:15.118550+08:00 SUCCESS: alter diskgroup data offline disk data_0005 2019-06-25T22:44:17.271264+08:00 WARNING: Started Drop Disk Timeout for Disk 5 (DATA_0005) in group 1 with a value 43200 WARNING: Disk 5 (DATA_0005) in group 1 will be dropped in: (43200) secs on ASM inst 1 |
这个43200秒就是disk repair time的12小时。fast mirror 开始工作了。
接下来在数据库中创建一个数据文件。以次来构造变化。
|
1 2 3 4 5 6 7 |
SQL> alter session set container=ora19pdb1; Session altered. SQL> create tablespace fmr datafile '+DATA/ORA19c/ORA19PDB1/fmr_001.dbf' size 8m; Tablespace created. |
|
1 |
1 277 fmr_001.dbf DATAFILE |
注意，这个文件是277号文件。我们查看他的AU分布：
|
1 2 3 4 5 6 7 8 9 10 |
Extent AU Disk # Disk name ---------- ---------- ---------- ------------------------------------------------------------------------------------------ 0 355 2 DATA_0002 364 4 DATA_0004 1 359 0 DATA_0000 365 4 DATA_0004 2 355 1 DATA_0001 366 4 DATA_0004 6 rows selected. |
可以看到这个8M的文件，分配了三个AU，AU是4M，因为ASM要附加一个block size的文件头，就是8M+8192K，所以要分配三个AU。
关掉数据库和Grid。
kfed读取12号文件，根据前文查出来的AU分布：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 |
kfbh.endian: 1 ; 0x000: 0x01 kfbh.hard: 130 ; 0x001: 0x82 kfbh.type: 21 ; 0x002: KFBTYP_STALEDIR kfbh.datfmt: 1 ; 0x003: 0x01 kfbh.block.blk: 0 ; 0x004: blk=0 kfbh.block.obj: 12 ; 0x008: file=12 kfbh.check: 1313736516 ; 0x00c: 0x4e4e0744 kfbh.fcn.base: 36726 ; 0x010: 0x00008f76 kfbh.fcn.wrap: 0 ; 0x014: 0x00000000 kfbh.spare1: 0 ; 0x018: 0x00000000 kfbh.spare2: 0 ; 0x01c: 0x00000000 kffdnd.bnode.incarn: 1 ; 0x000: A=1 NUMM=0x0 kffdnd.bnode.frlist.number: 4294967295 ; 0x004: 0xffffffff kffdnd.bnode.frlist.incarn: 0 ; 0x008: A=0 NUMM=0x0 kffdnd.overfl.number: 1 ; 0x00c: 0x00000001 kffdnd.overfl.incarn: 1 ; 0x010: A=1 NUMM=0x0 kffdnd.parent.number: 0 ; 0x014: 0x00000000 kffdnd.parent.incarn: 1 ; 0x018: A=1 NUMM=0x0 kffdnd.fstblk.number: 0 ; 0x01c: 0x00000000 kffdnd.fstblk.incarn: 1 ; 0x020: A=1 NUMM=0x0 kfdsde.entry.incarn: 1 ; 0x024: A=1 NUMM=0x0 kfdsde.entry.hash: 0 ; 0x028: 0x00000000 kfdsde.entry.refer.number: 4294967295 ; 0x02c: 0xffffffff kfdsde.entry.refer.incarn: 0 ; 0x030: A=0 NUMM=0x0 kfdsde.cid: shared_client_00001 ; 0x034: length=19 kfdsde.indlen: 5 ; 0x074: 0x0005 kfdsde.flags: 1 ; 0x076: 0x0001 kfdsde.spare1: 0 ; 0x078: 0x00000000 kfdsde.spare2: 0 ; 0x07c: 0x00000000 kfdsde.indices[0]: 0 ; 0x080: 0x00000000 kfdsde.indices[1]: 1 ; 0x084: 0x00000001 kfdsde.indices[2]: 2 ; 0x088: 0x00000002 kfdsde.indices[3]: 3 ; 0x08c: 0x00000003 kfdsde.indices[4]: 4 ; 0x090: 0x00000004 kfdsde.indices[5]: 0 ; 0x094: 0x00000000 kfdsde.indices[6]: 0 ; 0x098: 0x00000000 kfdsde.indices[7]: 0 ; 0x09c: 0x00000000 kfdsde.indices[8]: 0 ; 0x0a0: 0x00000000 kfdsde.indices[9]: 0 ; 0x0a4: 0x00000000 kfdsde.indices[10]: 0 ; 0x0a8: 0x00000000 |
尴尬，看不懂后面的fdsde.indices是什么意思，不过看是0到4，应该是指向了磁盘组剩余的5个盘。
重点是254号文件，我们之前查到的254号文件的AU分布，拿kfed读出来如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 |
kfbh.endian: 1 ; 0x000: 0x01 kfbh.hard: 130 ; 0x001: 0x82 kfbh.type: 20 ; 0x002: KFBTYP_SR kfbh.datfmt: 1 ; 0x003: 0x01 kfbh.block.blk: 0 ; 0x004: blk=0 kfbh.block.obj: 254 ; 0x008: file=254 kfbh.check: 3738159470 ; 0x00c: 0xdecfc96e kfbh.fcn.base: 0 ; 0x010: 0x00000000 kfbh.fcn.wrap: 0 ; 0x014: 0x00000000 kfbh.spare1: 0 ; 0x018: 0x00000000 kfbh.spare2: 0 ; 0x01c: 0x00000000 kfdsHdrB.clientId: 1331300926 ; 0x000: 0x4f5a0a3e kfdsHdrB.incarn: 0 ; 0x004: 0x00000000 kfdsHdrB.dskNum: 5 ; 0x008: 0x0005 - -这里记录的就是5号盘DATA_0005的记录。 kfdsHdrB.ub2spare: 0 ; 0x00a: 0x0000 --下面这些我猜测是记录5号盘不在了以后，磁盘组内发生了哪些变化，以供后期fast mirror resync来用。但是很遗憾啊看不懂。。。 ub1[0]: 4 ; 0x00c: 0x04 ub1[1]: 0 ; 0x00d: 0x00 ub1[2]: 128 ; 0x00e: 0x80 ub1[3]: 0 ; 0x00f: 0x00 ub1[4]: 32 ; 0x010: 0x20 ub1[5]: 0 ; 0x011: 0x00 ub1[6]: 0 ; 0x012: 0x00 ub1[7]: 0 ; 0x013: 0x00 ub1[8]: 0 ; 0x014: 0x00 ub1[9]: 32 ; 0x015: 0x20 ub1[10]: 2 ; 0x016: 0x02 ub1[11]: 2 ; 0x017: 0x02 ub1[12]: 0 ; 0x018: 0x00 ub1[13]: 130 ; 0x019: 0x82 ub1[14]: 128 ; 0x01a: 0x80 ub1[15]: 2 ; 0x01b: 0x02 ub1[16]: 0 ; 0x01c: 0x00 ub1[17]: 0 ; 0x01d: 0x00 ub1[18]: 4 ; 0x01e: 0x04 ub1[19]: 128 ; 0x01f: 0x80 ub1[20]: 0 ; 0x020: 0x00 ub1[21]: 0 ; 0x021: 0x00 ub1[22]: 0 ; 0x022: 0x00 ub1[23]: 48 ; 0x023: 0x30 ub1[24]: 6 ; 0x024: 0x06 ub1[25]: 0 ; 0x025: 0x00 ub1[26]: 0 ; 0x026: 0x00 ub1[27]: 0 ; 0x027: 0x00 ub1[28]: 128 ; 0x028: 0x80 ub1[29]: 0 ; 0x029: 0x00 ub1[30]: 2 ; 0x02a: 0x02 ub1[31]: 0 ; 0x02b: 0x00 ub1[32]: 0 ; 0x02c: 0x00 ub1[33]: 128 ; 0x02d: 0x80 ub1[34]: 129 ; 0x02e: 0x81 ub1[35]: 0 ; 0x02f: 0x00 ub1[36]: 8 ; 0x030: 0x08 ub1[37]: 0 ; 0x031: 0x00 ub1[38]: 0 ; 0x032: 0x00 ub1[39]: 32 ; 0x033: 0x20 ub1[40]: 0 ; 0x034: 0x00 ub1[41]: 99 ; 0x035: 0x63 ub1[42]: 4 ; 0x036: 0x04 ub1[43]: 0 ; 0x037: 0x00 ub1[44]: 0 ; 0x038: 0x00 ub1[45]: 0 ; 0x039: 0x00 ub1[46]: 0 ; 0x03a: 0x00 |
为了证明这些标识是记录了文件AU分布变化的，将这个磁盘online之后看这些标识是否会变化：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
kfbh.endian: 1 ; 0x000: 0x01 kfbh.hard: 130 ; 0x001: 0x82 kfbh.type: 20 ; 0x002: KFBTYP_SR kfbh.datfmt: 1 ; 0x003: 0x01 kfbh.block.blk: 0 ; 0x004: blk=0 kfbh.block.obj: 254 ; 0x008: file=254 kfbh.check: 4276836880 ; 0x00c: 0xfeeb5a10 kfbh.fcn.base: 0 ; 0x010: 0x00000000 kfbh.fcn.wrap: 0 ; 0x014: 0x00000000 kfbh.spare1: 0 ; 0x018: 0x00000000 kfbh.spare2: 0 ; 0x01c: 0x00000000 kfdsHdrB.clientId: 4294967295 ; 0x000: 0xffffffff kfdsHdrB.incarn: 0 ; 0x004: 0x00000000 kfdsHdrB.dskNum: 10000 ; 0x008: 0x2710 kfdsHdrB.ub2spare: 0 ; 0x00a: 0x0000 ub1[0]: 0 ; 0x00c: 0x00 ub1[1]: 0 ; 0x00d: 0x00 ub1[2]: 0 ; 0x00e: 0x00 ub1[3]: 0 ; 0x00f: 0x00 ub1[4]: 0 ; 0x010: 0x00 ub1[5]: 0 ; 0x011: 0x00 ub1[6]: 0 ; 0x012: 0x00 ub1[7]: 0 ; 0x013: 0x00 |
在磁盘online之后，ASM清除了这些标志位。说明fast mirror resync之后，这些标志位也没有意义了。
磁盘online的日志如下，信息量非常大：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 |
2019-06-25T23:16:49.757361+08:00 SQL> alter diskgroup data online disk data_0005 2019-06-25T23:16:49.758847+08:00 NOTE: cache closing disk 5 of grp 1: (not open) DATA_0005 2019-06-25T23:16:49.760802+08:00 NOTE: initiating resync of disk group 1 disks DATA_0005 (5) --日志里显示要开始resync这个磁盘组的这个磁盘了。 NOTE: process _user6684_+asm (6684) initiating offline of disk 5.4042336451 (DATA_0005) with mask 0x7e in group 1 (DATA) without client assisting -- 6684号进程是这个，可以考虑来在OS级别跟踪下：grid 6684 6683 0 2 2:58 ? 00:00:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 2019-06-25T23:16:49.762126+08:00 NOTE: sending set offline flag message (2308864632) to 1 disk(s) in group 1 2019-06-25T23:16:49.762818+08:00 WARNING: Disk 5 (DATA_0005) in group 1 mode 0x1 is now being offlined 2019-06-25T23:16:49.763495+08:00 NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0xf0f128c3, mask = 0x6a, op = clear mandatory --更新磁盘组PST信息 2019-06-25T23:16:49.764130+08:00 GMON updating disk modes for group 1 at 22 for pid 36, osid 6684 2019-06-25T23:16:49.765092+08:00 NOTE: cache closing disk 5 of grp 1: (not open) DATA_0005 2019-06-25T23:16:49.768554+08:00 NOTE: PST update grp = 1 completed successfully NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0xf0f128c3, mask = 0x7e, op = clear mandatory 2019-06-25T23:16:49.769939+08:00 GMON updating disk modes for group 1 at 23 for pid 36, osid 6684 2019-06-25T23:16:49.770816+08:00 NOTE: cache closing disk 5 of grp 1: (not open) DATA_0005 2019-06-25T23:16:49.776247+08:00 NOTE: PST update grp = 1 completed successfully NOTE: requesting all-instance membership refresh for group=1 NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0x0, mask = 0x11, op = assign mandatory 2019-06-25T23:16:49.779109+08:00 GMON updating disk modes for group 1 at 24 for pid 36, osid 6684 2019-06-25T23:16:49.779995+08:00 NOTE: cache closing disk 5 of grp 1: (not open) DATA_0005 2019-06-25T23:16:49.789961+08:00 NOTE: PST update grp = 1 completed successfully NOTE: requesting all-instance disk validation for group=1 2019-06-25T23:16:49.791043+08:00 NOTE: disk validation pending for 1 disk in group 1/0x9621d84c (DATA) NOTE: Found /dev/mapper/data06 for disk DATA_0005 NOTE: completed disk validation for 1/0x9621d84c (DATA) 2019-06-25T23:16:50.236934+08:00 NOTE: discarding redo for group 1 disk 5 NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0x0, mask = 0x19, op = assign mandatory 2019-06-25T23:16:50.256937+08:00 GMON updating disk modes for group 1 at 25 for pid 36, osid 6684 2019-06-25T23:16:50.268282+08:00 NOTE: PST update grp = 1 completed successfully 2019-06-25T23:16:50.402190+08:00 NOTE: membership refresh pending for group 1/0x9621d84c (DATA) 2019-06-25T23:16:50.405638+08:00 GMON querying group 1 at 26 for pid 19, osid 6103 NOTE: cache opening disk 5 of grp 1: DATA_0005 path:/dev/mapper/data06 2019-06-25T23:16:50.411361+08:00 SUCCESS: refreshed membership for 1/0x9621d84c (DATA) 2019-06-25T23:16:50.420753+08:00 NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0x0, mask = 0x5d, op = assign mandatory 2019-06-25T23:16:50.421332+08:00 GMON updating disk modes for group 1 at 27 for pid 36, osid 6684 2019-06-25T23:16:50.431570+08:00 NOTE: PST update grp = 1 completed successfully NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0x0, mask = 0x7d, op = assign mandatory 2019-06-25T23:16:50.432751+08:00 GMON updating disk modes for group 1 at 28 for pid 36, osid 6684 2019-06-25T23:16:50.440547+08:00 NOTE: PST update grp = 1 completed successfully 2019-06-25T23:16:50.442062+08:00 SUCCESS: alter diskgroup data online disk data_0005 2019-06-25T23:16:52.169010+08:00 NOTE: Attempting voting file refresh on diskgroup DATA 2019-06-25T23:16:52.200300+08:00 NOTE: starting rebalance of group 1/0x9621d84c (DATA) at power 1 NOTE: starting process ARBA Starting background process ARBA NOTE: starting process ARB0 Starting background process ARB0 2019-06-25T23:16:52.250256+08:00 ARBA started with pid=30, OS id=7912 2019-06-25T23:16:52.295116+08:00 ARB0 started with pid=31, OS id=7914 NOTE: assigning ARBA to group 1/0x9621d84c (DATA) to compute estimates NOTE: assigning ARB0 to group 1/0x9621d84c (DATA) with 1 parallel I/O 2019-06-25T23:16:52.315984+08:00 NOTE: Starting resync using Staleness Registry and ATE scan for group 1 -- 这里很明显的表示resync要用到Staleness Registry了 2019-06-25T23:16:58.481893+08:00 NOTE: Starting resync using Staleness Registry and ATE scan for group 1 NOTE: header on disk 5 advanced to format #2 using fcn 0.0 2019-06-25T23:17:04.765190+08:00 NOTE: F1X0 on disk 5 (fmt 2) relocated at fcn 0.36964: AU 0 -> AU 356 NOTE: F1B1 fcn on disk 4 synced at fcn 0.36964 NOTE: F1B1 fcn on disk 3 synced at fcn 0.36964 --这里提到了f1b1，就是ASM元数据的1号文件，这里表示1号文件的信息也被更新了。 2019-06-25T23:17:10.252489+08:00 NOTE: initiating PST update: grp 1 (DATA), dsk = 5/0x0, mask = 0x7f, op = assign mandatory 2019-06-25T23:17:10.253301+08:00 GMON updating disk modes for group 1 at 29 for pid 31, osid 7914 2019-06-25T23:17:10.263003+08:00 NOTE: PST update grp = 1 completed successfully NOTE: reset timers for disk: 5 NOTE: completed online of disk group 1 disks -- 重置了计时器，重置了5号盘的disk repair time。 DATA_0005 (5) 2019-06-25T23:17:10.274998+08:00 NOTE: stopping process ARBA NOTE: stopping process ARB0 NOTE: Starting expel slave for group 1/0x9621d84c (DATA) 2019-06-25T23:17:10.452719+08:00 NOTE: requesting all-instance membership refresh for group=1 2019-06-25T23:17:10.455438+08:00 NOTE: membership refresh pending for group 1/0x9621d84c (DATA) 2019-06-25T23:17:10.457973+08:00 GMON querying group 1 at 30 for pid 19, osid 6103 --6103是asm_rbal_+ASM进程，rebal完成了。 2019-06-25T23:17:10.459863+08:00 SUCCESS: refreshed membership for 1/0x9621d84c (DATA) 2019-06-25T23:17:13.259561+08:00 SUCCESS: rebalance completed for group 1/0x9621d84c (DATA) NOTE: Attempting voting file refresh on diskgroup DATA |
敏帝威武