mysql mount disk_asm disk误设置pvid导致asm diskgroup无法mount恢复

2023-10-11 20:10

本文主要是介绍mysql mount disk_asm disk误设置pvid导致asm diskgroup无法mount恢复,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

有朋友找到我说他们把以前存储到AIX直连的存储切换为含光纤交换机的存储网络后,RAC无法启动,让我给予支持.通过分析是由于换链路之后开始磁盘顺序不对,维护人员对其asm disk 设置了pvid,导致asm 磁盘组无法正常mount,从而使得含votedisk的dg的asm disk无法正常访问,从而RAC的cssd进程无法启动,同样数据文件的磁盘组也无法mount,通过kfed修复成功,实现数据0丢失.

平台版本信息(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:

[ohasd(6946818)]CRS-2769:Unable to failover resource 'ora.diskmon'.

2014-12-20 16:44:11.775:

[cssd(9502756)]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:

[cssd(9502756)]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:

[cssd(9502756)]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:

[cssd(10027070)]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:

[cssd(10027070)]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:

[cssd(10027070)]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: [kfbtTraverseBlock][Invalid OSM block type][][212]

$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]: 0 ; 0x00c: 0x00000000

kfdfsb.spare[1]: 0 ; 0x010: 0x00000000

kfdfsb.spare[2]: 0 ; 0x014: 0x00000000

kfdfse[0].fse: 119 ; 0x018: FREE=0x7 FRAG=0x7

kfdfse[1].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]: 0 ; 0x008: 0x00000000

kfdhdb.driver.reserved[1]: 0 ; 0x00c: 0x00000000

kfdhdb.driver.reserved[2]: 0 ; 0x010: 0x00000000

kfdhdb.driver.reserved[3]: 0 ; 0x014: 0x00000000

kfdhdb.driver.reserved[4]: 0 ; 0x018: 0x00000000

kfdhdb.driver.reserved[5]: 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 被破坏,进一步分析破坏原因

[db2/dev#]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

[db2/dev#]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 REDUNDANCY DISK '/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 REDUNDANCY DISK

'/dev/rhdisk9' SIZE 614400M ATTRIBUTE '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 REDUNDANCY DISK

'/dev/rhdisk8' SIZE 204800M ATTRIBUTE '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 REDUNDANCY DISK

'/dev/rhdisk7' SIZE 102400M ATTRIBUTE '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[4-9],通过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状态也恢复正常

[db2/#]crsctl status res -t

--------------------------------------------------------------------------------

NAME TARGET STATE SERVER STATE_DETAILS

--------------------------------------------------------------------------------

Local Resources

--------------------------------------------------------------------------------

ora.ARCH.dg

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.CRS.dg

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.DATA.dg

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.FBA.dg

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.LISTENER.lsnr

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.asm

ONLINE ONLINE db1 Started

ONLINE ONLINE db2 Started

ora.gsd

OFFLINE OFFLINE db1

OFFLINE OFFLINE db2

ora.net1.network

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.ons

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.registry.acfs

ONLINE ONLINE db1

ONLINE ONLINE db2

--------------------------------------------------------------------------------

Cluster Resources

--------------------------------------------------------------------------------

ora.LISTENER_SCAN1.lsnr

1 ONLINE ONLINE db1

ora.cvu

1 ONLINE ONLINE db1

ora.db1.vip

1 ONLINE ONLINE db1

ora.db2.vip

1 ONLINE ONLINE db2

ora.nkora.db

1 ONLINE ONLINE db1 Open

2 ONLINE ONLINE db2 Open

ora.oc4j

1 ONLINE ONLINE db1

ora.scan1.vip

1 ONLINE ONLINE db1

这里忽略了一个问题,在修复磁盘头之前没有清除pvid,导致磁盘头修复后,pvid依然存储在odm中

[db2/dev#]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

[db2/#]chdev -l hdisk8 -a pv=clear

hdisk8 changed

[db2/#]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

[db2/#]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[4-9]所有pvid,启动GI一切正常

[db1/#]crsctl status res -t

--------------------------------------------------------------------------------

NAME TARGET STATE SERVER STATE_DETAILS

--------------------------------------------------------------------------------

Local Resources

--------------------------------------------------------------------------------

ora.ARCH.dg

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.CRS.dg

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.DATA.dg

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.FBA.dg

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.LISTENER.lsnr

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.asm

ONLINE ONLINE db1 Started

ONLINE ONLINE db2 Started

ora.gsd

OFFLINE OFFLINE db1

OFFLINE OFFLINE db2

ora.net1.network

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.ons

ONLINE ONLINE db1

ONLINE ONLINE db2

ora.registry.acfs

ONLINE ONLINE db1

ONLINE ONLINE db2

--------------------------------------------------------------------------------

Cluster Resources

--------------------------------------------------------------------------------

ora.LISTENER_SCAN1.lsnr

1 ONLINE ONLINE db1

ora.cvu

1 ONLINE ONLINE db1

ora.db1.vip

1 ONLINE ONLINE db1

ora.db2.vip

1 ONLINE ONLINE db2

ora.nkora.db

1 ONLINE ONLINE db1 Open

2 ONLINE ONLINE db2 Open

ora.oc4j

1 ONLINE ONLINE db1

ora.scan1.vip

1 ONLINE ONLINE db1

[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

如果您遇到此类情况,无法解决请联系我们,提供专业ORACLE数据库恢复技术支持

Phone:13429648788    Q Q:107644445070b0066bacfd9eecef93af3f89813bc.png    E-Mail:dba@xifenfei.com

这篇关于mysql mount disk_asm disk误设置pvid导致asm diskgroup无法mount恢复的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/190521

相关文章

MySQL数据库双机热备的配置方法详解

《MySQL数据库双机热备的配置方法详解》在企业级应用中,数据库的高可用性和数据的安全性是至关重要的,MySQL作为最流行的开源关系型数据库管理系统之一,提供了多种方式来实现高可用性,其中双机热备(M... 目录1. 环境准备1.1 安装mysql1.2 配置MySQL1.2.1 主服务器配置1.2.2 从

深入理解Mysql OnlineDDL的算法

《深入理解MysqlOnlineDDL的算法》本文主要介绍了讲解MysqlOnlineDDL的算法,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面随着小... 目录一、Online DDL 是什么?二、Online DDL 的三种主要算法2.1COPY(复制法)

mysql8.0.43使用InnoDB Cluster配置主从复制

《mysql8.0.43使用InnoDBCluster配置主从复制》本文主要介绍了mysql8.0.43使用InnoDBCluster配置主从复制,文中通过示例代码介绍的非常详细,对大家的学习或者... 目录1、配置Hosts解析(所有服务器都要执行)2、安装mysql shell(所有服务器都要执行)3、

k8s中实现mysql主备过程详解

《k8s中实现mysql主备过程详解》文章讲解了在K8s中使用StatefulSet部署MySQL主备架构,包含NFS安装、storageClass配置、MySQL部署及同步检查步骤,确保主备数据一致... 目录一、k8s中实现mysql主备1.1 环境信息1.2 部署nfs-provisioner1.2.

MySQL中VARCHAR和TEXT的区别小结

《MySQL中VARCHAR和TEXT的区别小结》MySQL中VARCHAR和TEXT用于存储字符串,VARCHAR可变长度存储在行内,适合短文本;TEXT存储在溢出页,适合大文本,下面就来具体的了解... 目录一、VARCHAR 和 TEXT 基本介绍1. VARCHAR2. TEXT二、VARCHAR

MySQL中C接口的实现

《MySQL中C接口的实现》本节内容介绍使用C/C++访问数据库,包括对数据库的增删查改操作,主要是学习一些接口的调用,具有一定的参考价值,感兴趣的可以了解一下... 目录准备mysql库使用mysql库编译文件官方API文档对象的创建和关闭链接数据库下达sql指令select语句前言:本节内容介绍使用C/

mybatis直接执行完整sql及踩坑解决

《mybatis直接执行完整sql及踩坑解决》MyBatis可通过select标签执行动态SQL,DQL用ListLinkedHashMap接收结果,DML用int处理,注意防御SQL注入,优先使用#... 目录myBATiFBNZQs直接执行完整sql及踩坑select语句采用count、insert、u

MySQL之搜索引擎使用解读

《MySQL之搜索引擎使用解读》MySQL存储引擎是数据存储和管理的核心组件,不同引擎(如InnoDB、MyISAM)采用不同机制,InnoDB支持事务与行锁,适合高并发场景;MyISAM不支持事务,... 目录mysql的存储引擎是什么MySQL存储引擎的功能MySQL的存储引擎的分类查看存储引擎1.命令

Java实现为PDF设置背景色和背景图片

《Java实现为PDF设置背景色和背景图片》在日常的文档处理中,PDF格式因其稳定性和跨平台兼容性而广受欢迎,本文将深入探讨如何利用Spire.PDFforJava库,以简洁高效的方式为你的PDF文档... 目录库介绍与安装步骤Java 给 PDF 设置背景颜色Java 给 PDF 设置背景图片总结在日常的

C#中通过Response.Headers设置自定义参数的代码示例

《C#中通过Response.Headers设置自定义参数的代码示例》:本文主要介绍C#中通过Response.Headers设置自定义响应头的方法,涵盖基础添加、安全校验、生产实践及调试技巧,强... 目录一、基础设置方法1. 直接添加自定义头2. 批量设置模式二、高级配置技巧1. 安全校验机制2. 类型