设置pvid导致asm disk损坏,asm diskgroup无法mount
平台版本信息(2节点RAC)
$ sqlplus -v
SQL*Plus: Release 11.2.0.4.0 Production
$ uname -a
AIX db2 1 7 00F9733E4C00
GI日志报错信息
2014-12-20 16:44:08.769:
CRS-2769:Unable to failover resource 'ora.diskmon'.
2014-12-20 16:44:11.775:
CRS-1714:Unable to discover any voting files, retrying discovery in 15 seconds;
Details at (:CSSNM00070:) in /u01/app/11.2.0/grid/log/db1/cssd/ocssd.log
2014-12-20 16:44:26.791:
CRS-1714:Unable to discover any voting files, retrying discovery in 15 seconds;
、Details at (:CSSNM00070:) in /u01/app/11.2.0/grid/log/db1/cssd/ocssd.log
2014-12-20 16:44:41.812:
CRS-1714:Unable to discover any voting files, retrying discovery in 15 seconds;
Details at (:CSSNM00070:) in /u01/app/11.2.0/grid/log/db1/cssd/ocssd.log
从这里可以看出来是由于RAC启动过程中无法获得votedisk使得其无法正常启动,通过分析日志找出来votedisk相关磁盘
2014-12-15 17:36:15.424:
CRS-1605:CSSD voting file is online: /dev/rhdisk4; details in /u01/app/11.2.0/grid/log/db1/cssd/ocssd.log
2014-12-15 17:36:15.433:
CRS-1605:CSSD voting file is online: /dev/rhdisk5; details in /u01/app/11.2.0/grid/log/db1/cssd/ocssd.log
2014-12-15 17:36:15.445:
CRS-1605:CSSD voting file is online: /dev/rhdisk6; details in /u01/app/11.2.0/grid/log/db1/cssd/ocssd.log
从这里可以知道rhdisk4,5,6为votedisk对应磁盘,使用kfed查看磁盘头信息
$kfed read /dev/rhdisk4
kfbh.endian: 201 ; 0x000: 0xc9
kfbh.hard: 194 ; 0x001: 0xc2
kfbh.type: 212 ; 0x002: *** Unknown Enum ***
kfbh.datfmt: 193 ; 0x003: 0xc1
kfbh.block.blk: 0 ; 0x004: blk=0
kfbh.block.obj: 0 ; 0x008: file=0
kfbh.check: 0 ; 0x00c: 0x00000000
kfbh.fcn.base: 0 ; 0x010: 0x00000000
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
1102BEE00 C9C2D4C1 00000000 00000000 00000000[................]
1102BEE10 00000000 00000000 00000000 00000000[................]
Repeat 6 times
1102BEE80 00F9733D 67553E0A 00000000 00000000[..s=gU>.........]
1102BEE90 00000000 00000000 00000000 00000000[................]
Repeat 246 times
KFED-00322: Invalid content encountered during block traversal: []
$kfed read /dev/rhdisk4 blkn=1
kfbh.endian: 0 ; 0x000: 0x00
kfbh.hard: 130 ; 0x001: 0x82
kfbh.type: 2 ; 0x002: KFBTYP_FREESPC
kfbh.datfmt: 2 ; 0x003: 0x02
kfbh.block.blk: 1 ; 0x004: blk=1
kfbh.block.obj: 2147483648 ; 0x008: disk=0
kfbh.check: 3883664132 ; 0x00c: 0xe77c0304
kfbh.fcn.base: 0 ; 0x010: 0x00000000
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
kfdfsb.aunum: 0 ; 0x000: 0x00000000
kfdfsb.max: 254 ; 0x004: 0x00fe
kfdfsb.cnt: 23 ; 0x006: 0x0017
kfdfsb.bound: 0 ; 0x008: 0x0000
kfdfsb.flag: 1 ; 0x00a: B=1
kfdfsb.ub1spare: 0 ; 0x00b: 0x00
kfdfsb.spare: 0 ; 0x00c: 0x00000000
kfdfsb.spare: 0 ; 0x010: 0x00000000
kfdfsb.spare: 0 ; 0x014: 0x00000000
kfdfse.fse: 119 ; 0x018: FREE=0x7 FRAG=0x7
kfdfse.fse: 16 ; 0x019: FREE=0x0 FRAG=0x1
…………
$kfed read /dev/rhdisk4 blkn=510
kfbh.endian: 0 ; 0x000: 0x00
kfbh.hard: 130 ; 0x001: 0x82
kfbh.type: 1 ; 0x002: KFBTYP_DISKHEAD
kfbh.datfmt: 1 ; 0x003: 0x01
kfbh.block.blk: 254 ; 0x004: blk=254
kfbh.block.obj: 2147483648 ; 0x008: disk=0
kfbh.check: 3460116983 ; 0x00c: 0xce3d31f7
kfbh.fcn.base: 0 ; 0x010: 0x00000000
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
kfdhdb.driver.provstr: ORCLDISK ; 0x000: length=8
kfdhdb.driver.reserved: 0 ; 0x008: 0x00000000
kfdhdb.driver.reserved: 0 ; 0x00c: 0x00000000
kfdhdb.driver.reserved: 0 ; 0x010: 0x00000000
kfdhdb.driver.reserved: 0 ; 0x014: 0x00000000
kfdhdb.driver.reserved: 0 ; 0x018: 0x00000000
kfdhdb.driver.reserved: 0 ; 0x01c: 0x00000000
kfdhdb.compat: 186646528 ; 0x020: 0x0b200000
kfdhdb.dsknum: 0 ; 0x024: 0x0000
kfdhdb.grptyp: 2 ; 0x026: KFDGTP_NORMAL
kfdhdb.hdrsts: 3 ; 0x027: KFDHDR_MEMBER
kfdhdb.dskname: CRS_0000 ; 0x028: length=8
kfdhdb.grpname: CRS ; 0x048: length=3
kfdhdb.fgname: CRS_0000 ; 0x068: length=8
…………
由上述分析可以基本上确定是asm disk header 被破坏,进一步分析破坏原因
lspv
hdisk0 00f9733ef7cf27e9 rootvg active
hdisk1 00f9733e21b953e6 rootvg active
hdisk2 00f9733e21b97a83 appvg active
hdisk3 00f9733e21b98434 appvg active
hdisk4 00f9733d67553e0a None
hdisk5 00f9733d67553f31 None
hdisk6 00f9733d67554011 None
hdisk7 00f9733d67554165 None
hdisk8 00f9733d675541e5 None
hdisk9 00f9733d675542e4 None
hdisk10 none None
ls -l rhdisk*
crw------- 2 root system 24,1 Oct 18 11:45 rhdisk0
crw------- 1 root system 24,3 Oct 18 13:27 rhdisk1
crw------- 1 root system 24,5 Dec 20 20:02 rhdisk10
crw------- 1 root system 24,2 Oct 18 13:32 rhdisk2
crw------- 1 root system 24,0 Oct 18 13:32 rhdisk3
crw-rw---- 1 grid asmadmin 24,8 Dec 20 20:02 rhdisk4
crw-rw---- 1 grid asmadmin 24,9 Dec 20 20:02 rhdisk5
crw-rw---- 1 grid asmadmin 24, 10 Dec 20 20:02 rhdisk6
crw-rw---- 1 grid asmadmin 24,4 Dec 20 20:02 rhdisk7
crw-rw---- 1 grid asmadmin 24,6 Dec 20 20:02 rhdisk8
crw-rw---- 1 grid asmadmin 24,7 Dec 20 20:02 rhdisk9
从这里基本上可以看出来,是由于磁盘头被重写了pvid,导致asm disk header 被破坏.进一步分析asm log,确定哪些磁盘被用作asm disk
SQL> CREATE DISKGROUP CRS NORMAL REDUNDANCYDISK '/dev/rhdisk4',
'/dev/rhdisk5',
'/dev/rhdisk6' ATTRIBUTE 'compatible.asm'='11.2.0.0.0','au_size'='1M' /* ASMCA */
NOTE: Assigning number (1,0) to disk (/dev/rhdisk4)
NOTE: Assigning number (1,1) to disk (/dev/rhdisk5)
NOTE: Assigning number (1,2) to disk (/dev/rhdisk6)
NOTE: initializing header on grp 1 disk CRS_0000
NOTE: initializing header on grp 1 disk CRS_0001
NOTE: initializing header on grp 1 disk CRS_0002
SQL> CREATE DISKGROUP DATA EXTERNAL REDUNDANCYDISK
'/dev/rhdisk9' SIZE 614400MATTRIBUTE 'compatible.asm'='11.2.0.0.0','au_size'='1M' /* ASMCA */
NOTE: Assigning number (2,0) to disk (/dev/rhdisk9)
NOTE: initializing header on grp 2 disk DATA_0000
SQL> CREATE DISKGROUP FBA EXTERNAL REDUNDANCYDISK
'/dev/rhdisk8' SIZE 204800MATTRIBUTE 'compatible.asm'='11.2.0.0.0','au_size'='1M' /* ASMCA */
NOTE: Assigning number (3,0) to disk (/dev/rhdisk8)
NOTE: initializing header on grp 3 disk FBA_0000
SQL> CREATE DISKGROUP ARCH EXTERNAL REDUNDANCYDISK
'/dev/rhdisk7' SIZE 102400MATTRIBUTE 'compatible.asm'='11.2.0.0.0','au_size'='1M' /* ASMCA */
NOTE: Assigning number (4,0) to disk (/dev/rhdisk7)
NOTE: initializing header on grp 4 disk ARCH_0000
这里可以确定asm disk为rhdisk,通过kfed分析全部和rhdisk4一样的问题,也符合lspv查询出来的结果,使用kfed repair修复asm disk header后
SQL> alter diskgroup data mount;
Diskgroup altered.
SQL> alter diskgroup fba mount;
Diskgroup altered.
SQL> alter diskgroup arch mount;
Diskgroup altered.
SQL> alter diskgroup crs mount;
Diskgroup altered.
SQL> select group_number,disk_number,path from v$asm_disk;
GROUP_NUMBER DISK_NUMBER PATH
------------ ----------- --------------------------------------------------
2 0 /dev/rhdisk4
2 1 /dev/rhdisk5
2 2 /dev/rhdisk6
1 0 /dev/rhdisk7
4 0 /dev/rhdisk8
3 0 /dev/rhdisk9
6 rows selected.
SQL> select group_number,name from v$asm_diskgroup;
GROUP_NUMBER NAME
------------ ------------------------------------------------------------
1 ARCH
2 CRS
3 DATA
4 FBA
这里证明通过kfed对磁盘头的修复,asm磁盘组已经全部mount成功,GI状态也恢复正常
crsctl status res -t
--------------------------------------------------------------------------------
NAME TARGETSTATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ARCH.dg
ONLINEONLINE db1
ONLINEONLINE db2
ora.CRS.dg
ONLINEONLINE db1
ONLINEONLINE db2
ora.DATA.dg
ONLINEONLINE db1
ONLINEONLINE db2
ora.FBA.dg
ONLINEONLINE db1
ONLINEONLINE db2
ora.LISTENER.lsnr
ONLINEONLINE db1
ONLINEONLINE db2
ora.asm
ONLINEONLINE db1 Started
ONLINEONLINE db2 Started
ora.gsd
OFFLINE OFFLINE db1
OFFLINE OFFLINE db2
ora.net1.network
ONLINEONLINE db1
ONLINEONLINE db2
ora.ons
ONLINEONLINE db1
ONLINEONLINE db2
ora.registry.acfs
ONLINEONLINE db1
ONLINEONLINE db2
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
1 ONLINEONLINE db1
ora.cvu
1 ONLINEONLINE db1
ora.db1.vip
1 ONLINEONLINE db1
ora.db2.vip
1 ONLINEONLINE db2
ora.nkora.db
1 ONLINEONLINE db1 Open
2 ONLINEONLINE db2 Open
ora.oc4j
1 ONLINEONLINE db1
ora.scan1.vip
1 ONLINEONLINE db1
这里忽略了一个问题,在修复磁盘头之前没有清除pvid,导致磁盘头修复后,pvid依然存储在odm中
lspv
hdisk0 00f9733ef7cf27e9 rootvg active
hdisk1 00f9733e21b953e6 rootvg active
hdisk2 00f9733e21b97a83 appvg active
hdisk3 00f9733e21b98434 appvg active
hdisk4 00f9733d67553e0a None
hdisk5 00f9733d67553f31 None
hdisk6 00f9733d67554011 None
hdisk7 00f9733d67554165 None
hdisk8 00f9733d675541e5 None
hdisk9 00f9733d675542e4 None
hdisk10 none None
通过分析发现fba磁盘组中无任何记录,使用该磁盘组进行直接清除pvid测试
$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.4.0 Production on Sun Dec 21 03:13:31 2014
Copyright (c) 1982, 2013, Oracle.All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options
SQL> alter diskgroup fba dismount;
Diskgroup altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options
$ exit
You have mail in /usr/spool/mail/root
chdev -l hdisk8 -a pv=clear
hdisk8 changed
lspv
hdisk0 00f9733ef7cf27e9 rootvg active
hdisk1 00f9733e21b953e6 rootvg active
hdisk2 00f9733e21b97a83 appvg active
hdisk3 00f9733e21b98434 appvg active
hdisk4 00f9733d67553e0a None
hdisk5 00f9733d67553f31 None
hdisk6 00f9733d67554011 None
hdisk7 00f9733d67554165 None
hdisk8 none None
hdisk9 00f9733d675542e4 None
hdisk10 none None
su - grid
$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.4.0 Production on Sun Dec 21 03:15:19 2014
Copyright (c) 1982, 2013, Oracle.All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options
SQL> alter diskgroup fba mount;
Diskgroup altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options
通过测试直接清除pvid asm 磁盘头依然工作正常,关闭GI,使用chdev清除hdisk所有pvid,启动GI一切正常
crsctl status res -t
--------------------------------------------------------------------------------
NAME TARGETSTATE SERVER STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ARCH.dg
ONLINEONLINE db1
ONLINEONLINE db2
ora.CRS.dg
ONLINEONLINE db1
ONLINEONLINE db2
ora.DATA.dg
ONLINEONLINE db1
ONLINEONLINE db2
ora.FBA.dg
ONLINEONLINE db1
ONLINEONLINE db2
ora.LISTENER.lsnr
ONLINEONLINE db1
ONLINEONLINE db2
ora.asm
ONLINEONLINE db1 Started
ONLINEONLINE db2 Started
ora.gsd
OFFLINE OFFLINE db1
OFFLINE OFFLINE db2
ora.net1.network
ONLINEONLINE db1
ONLINEONLINE db2
ora.ons
ONLINEONLINE db1
ONLINEONLINE db2
ora.registry.acfs
ONLINEONLINE db1
ONLINEONLINE db2
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
1 ONLINEONLINE db1
ora.cvu
1 ONLINEONLINE db1
ora.db1.vip
1 ONLINEONLINE db1
ora.db2.vip
1 ONLINEONLINE db2
ora.nkora.db
1 ONLINEONLINE db1 Open
2 ONLINEONLINE db2 Open
ora.oc4j
1 ONLINEONLINE db1
ora.scan1.vip
1 ONLINEONLINE db1
lspv
hdisk0 00f9733df7c7a9db rootvg active
hdisk1 00f9733d21dad8fe rootvg active
hdisk2 00f9733d21dbd08b appvg active
hdisk3 00f9733d21dbd2ab appvg active
hdisk4 none None
hdisk5 none None
hdisk6 none None
hdisk7 none None
hdisk8 none None
hdisk9 none None
hdisk10 none None
至此设置pvid导致asm disk header损坏的asm 恢复正常,实现数据0丢失。
温馨提示:aix asm disk磁盘中不能设置pvid,否则将会导致asm disk header 损坏,无法正常mount
具体参考：asm disk误设置pvid导致asm diskgroup无法mount恢复
学习了 :)
页:
[1]