pvcreate asm disk導致asm磁碟組異常恢復---惜分飛
阿新 • • 發佈：2022-05-29
聯絡：手機/微信(+86 17813235971) QQ(107644445)
標題：pvcreate asm disk導致asm磁碟組異常恢復
作者：惜分飛©版權所有[未經本人同意,不得以任何形式轉載,否則有進一步追究法律責任的權利.]
一客戶asm磁碟組異常，無法正常mount
SQL> alter diskgroup datadg mount
2022-05-28T19:08:55.114960+08:00
NOTE: cache registered group DATADG 1/0x2B504997
NOTE: cache began mount (first) of group DATADG 1/0x2B504997
NOTE: Assigning number (1,3) to disk (/dev/oracleasm/disks/DATA05)
NOTE: Assigning number (1,2) to disk (/dev/oracleasm/disks/DATA03)
NOTE: Assigning number (1,1) to disk (/dev/oracleasm/disks/DATA02)
2022-05-28T19:08:55.150062+08:00
ERROR: no read quorum in group: required 1, found 0 disks
2022-05-28T19:08:55.150684+08:00NOTE: cache dismounting (clean) group 1/0x2B504997 (DATADG)
NOTE: messaging CKPT to quiesce pins Unix process pid: 15103, image: oracle@XFF01 (TNS V1-V3)
NOTE: dbwr not being msg'd to dismount
NOTE: LGWR not being messaged to dismount
NOTE: cache dismounted group 1/0x2B504997 (DATADG)
NOTE: cache ending mount (fail) of group DATADG number=1 incarn=0x2b504997
NOTE: cache deleting context for group DATADG 1/0x2b504997
2022-05-28T19:08:55.191073+08:00
GMON dismounting group 1 at 36 for pid 37, osid 15103
2022-05-28T19:08:55.191258+08:00
NOTE: Disk DATA02 in mode 0x8 marked for de-assignment
NOTE: Disk DATA03 in mode 0x8 marked for de-assignment
NOTE: Disk DATA05 in mode 0x8 marked for de-assignment
ERROR: diskgroup DATADG was not mounted
ORA-15032: not all alterations performed
ORA-15017: diskgroup "DATADG" cannot be mounted
ORA-15040: diskgroup is incomplete
|
通過報錯資訊,初步判斷是由於少了asm disk導致（依據:1. ORA-15040,2.asmlib中的DATA01丟失),初步判斷由於某種原因導致asmlib的磁碟異常,從而使得asm磁碟組無法正常mount,通過對dd 到本地的asm磁碟進行分析
C:\Users\XFF>kfed read H:\TEMP\asmdd\sdb6-o.dd
kfbh.endian: 0 ; 0x000: 0x00
kfbh.hard: 0 ; 0x001: 0x00
kfbh.type: 0 ; 0x002: KFBTYP_INVALID
kfbh.datfmt: 0 ; 0x003: 0x00
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
0066E8200 00000000 00000000 00000000 00000000 [................]
Repeat 31 times
0066E8400 4542414C 454E4F4C 00000001 00000000 [LABELONE........]
0066E8410 4E06D490 00000020 324D564C 31303020 [...N ...LVM2 001]
0066E8420 34535542 476A7667 42546C48 6D384675 [BUS4gvjGHlTBuF8m]
0066E8430 7A385273 4B495777 73336242 33637449 [sR8zwWIKBb3sItc3]
0066E8440 48001000 000001E8 00100000 00000000 [...H............]
0066E8450 00000000 00000000 00000000 00000000 [................]
0066E8460 00000000 00000000 00001000 00000000 [................]
0066E8470 000FF000 00000000 00000000 00000000 [................]
0066E8480 00000000 00000000 00000002 00000000 [................]
0066E8490 00000000 00000000 00000000 00000000 [................]
Repeat 214 times
KFED-00322: Invalid content encountered during block traversal: [kfbtTraverseBlock][Invalid OSM block type][][0]
|
通過這部分資訊可以確認，一個asm disk被建立了pv,進一步分析pv資訊
對於這樣的情況，表示asm disk被建立了pv但是pv沒有加入到任何vg中,也就意味著該disk沒有太大破壞,通過資訊確認
主要是這兩個部分資訊被損壞,可以通過一些方法對這兩個block資訊進行重構
C:\Users\XFF>kfed read H:\TEMP\asmdd\sdb6.dd|more
kfbh.endian: 1 ; 0x000: 0x01
kfbh.hard: 130 ; 0x001: 0x82
kfbh.type: 1 ; 0x002: KFBTYP_DISKHEAD
kfbh.datfmt: 1 ; 0x003: 0x01
kfbh.block.blk: 0 ; 0x004: blk=0
kfbh.block.obj: 2147483648 ; 0x008: disk=0
kfbh.check: 3196491921 ; 0x00c: 0xbe869891
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: ORCLDISKDATA01 ; 0x000: length=14
kfdhdb.driver.reserved[0]: 1096040772 ; 0x008: 0x41544144
kfdhdb.driver.reserved[1]: 12592 ; 0x00c: 0x00003130
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: 203424000 ; 0x020: 0x0c200100
kfdhdb.dsknum: 0 ; 0x024: 0x0000
kfdhdb.grptyp: 1 ; 0x026: KFDGTP_EXTERNAL
kfdhdb.hdrsts: 3 ; 0x027: KFDHDR_MEMBER
kfdhdb.dskname: DATA01 ; 0x028: length=6
kfdhdb.grpname: DATADG ; 0x048: length=6
kfdhdb.fgname: DATA01 ; 0x068: length=6
kfdhdb.capname: ; 0x088: length=0
kfdhdb.crestmp.hi: 33083792 ; 0x0a8: HOUR=0x10 DAYS=0xc MNTH=0x4 YEAR=0x7e3
kfdhdb.crestmp.lo: 2268043264 ; 0x0ac: USEC=0x0 MSEC=0x3e6 SECS=0x32 MINS=0x21
kfdhdb.mntstmp.hi: 33134479 ; 0x0b0: HOUR=0xf DAYS=0x1c MNTH=0x5 YEAR=0x7e6
-- More --
C:\Users\XFF>kfed read H:\TEMP\asmdd\sdb6.dd blkn=1|more
kfbh.endian: 1 ; 0x000: 0x01
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: 2177715180 ; 0x00c: 0x81cd4bec
kfbh.fcn.base: 3721754 ; 0x010: 0x0038ca1a
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
kfdfsb.aunum: 0 ; 0x000: 0x00000000
kfdfsb.max: 1014 ; 0x004: 0x03f6
kfdfsb.cnt: 1014 ; 0x006: 0x03f6
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: 0 ; 0x018: FREE=0x0 FRAG=0x0
kfdfse[1].fse: 0 ; 0x019: FREE=0x0 FRAG=0x0
kfdfse[2].fse: 0 ; 0x01a: FREE=0x0 FRAG=0x0
kfdfse[3].fse: 0 ; 0x01b: FREE=0x0 FRAG=0x0
kfdfse[4].fse: 0 ; 0x01c: FREE=0x0 FRAG=0x0
kfdfse[5].fse: 0 ; 0x01d: FREE=0x0 FRAG=0x0
kfdfse[6].fse: 0 ; 0x01e: FREE=0x0 FRAG=0x0
kfdfse[7].fse: 0 ; 0x01f: FREE=0x0 FRAG=0x0
kfdfse[8].fse: 0 ; 0x020: FREE=0x0 FRAG=0x0
|
通過dd寫入到原磁碟,通過oracleasm scandisks掃描磁碟
磁碟組mount成功
資料庫順利open
這個案例能夠完美恢復,主要是客戶沒有做進一步破壞，沒有把這個pv加入到vg中並且寫入資料,以前有過類似案例因為寫入了資料,恢復比這個難多了,效果也沒有這個好asm disk被加入vg恢復
如果不幸有類似oracle asm disk被破壞(格式化,dd部分,做成lv等),需要進行恢復支援,可以聯絡我們,做專業的恢復評估,最大限度,最快速度搶救資料,減少損失
Phone:17813235971 Q Q:107644445 E-Mail:[email protected]
恢復過部分asm異常案例:
刪除分割槽 oracle asm disk 恢復
asm disk 磁碟部分被清空恢復
又一例asm格式化檔案系統恢復
一次完美的asm disk被格式化ntfs恢復
oracle asm disk格式化恢復—格式化為ext4檔案系統
oracle asm disk格式化恢復—格式化為ntfs檔案系統
分享oracleasm createdisk重新建立asm disk後資料0丟失恢復案例
- asm disk 磁碟部分被清空恢復
- pvid=yes導致asm無法mount
- ERROR: diskgroup XXXX was not mounted
- 刪除分割槽 oracle asm disk 恢復
- 通過kfed說明asm disk header定義
- Physically Addressed Metadata Redundancy on 12c ASM ( PHYS_META_REPLICATED )
- ORA-15130: diskgroup “ORADATA” is being dismounted
- KFED-00322: Invalid content encountered during block traversal: [kfbtTraverseBlock][Invalid OSM block type]
- ASM DISK HEADER 備份與恢復
- 手工修復ASM DISK HEADER 異常
- 使用asm disk header 自動備份資訊恢復異常asm disk header
- asm磁碟分割槽丟失恢復