我这边的环境是2台P550+2台DS5020存储
做的是AIX-HACMP-LVM Mirror
两个Oracle实例,各跑在一台P550上,另一台为对方的备机
hdisk3 hdisk5为镜像盘,P550_A上的存储数据盘
但是在P550_B上实际中是没有挂载的。但是提示警告,另外还有一些警告,具体日志如下
---------------------------------------------------------------------------
LABEL: SC_DISK_ERR2
IDENTIFIER: B6267342
Date/Time: Wed May 25 10:22:30 2016
Sequence Number: 80378
Machine Id: 00CE0C954C00
Node Id: ahyyhis
Class: H
Type: PERM
WPAR: Global
Resource Name: hdisk5
Resource Class:
Resource Type:
Location:
VPD:
Manufacturer................IBM
Machine Type and Model......1814 FAStT
ROS Level and ID............31303630
Serial Number...............
Device Specific.(Z0)........0000053245005032
Device Specific.(Z1)........
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
PATH ID
0
SENSE DATA
0A00 2800 0000 0007 0000 0104 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0009 0002 6DC0 0000 0000 0000 0000 0000 0000 0000 0093 0000
0000 003D 0017
---------------------------------------------------------------------------
LABEL: SC_DISK_ERR2
IDENTIFIER: B6267342
Date/Time: Wed May 25 10:22:30 2016
Sequence Number: 80377
Machine Id: 00CE0C954C00
Node Id: ahyyhis
Class: H
Type: PERM
WPAR: Global
Resource Name: hdisk5
Resource Class:
Resource Type:
Location:
VPD:
Manufacturer................IBM
Machine Type and Model......1814 FAStT
ROS Level and ID............31303630
Serial Number...............
Device Specific.(Z0)........0000053245005032
Device Specific.(Z1)........
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
PATH ID
0
SENSE DATA
0600 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0009 0002 6DC0 0000 0000 0000 0000 0000 0000 0000 0093 0000
0000 003D 001A
---------------------------------------------------------------------------
LABEL: SC_DISK_ERR2
IDENTIFIER: B6267342
Date/Time: Wed May 25 10:22:30 2016
Sequence Number: 80376
Machine Id: 00CE0C954C00
Node Id: ahyyhis
Class: H
Type: PERM
WPAR: Global
Resource Name: hdisk3
Resource Class:
Resource Type:
Location:
VPD:
Manufacturer................IBM
Machine Type and Model......1814 FAStT
ROS Level and ID............31303630
Serial Number...............
Device Specific.(Z0)........0000053245005032
Device Specific.(Z1)........
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
PATH ID
0
SENSE DATA
0A00 2800 0000 0007 0000 0104 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0012 0000 D980 0000 0000 0000 0000 0000 0000 0000 0093 0000
0000 003D 0017
---------------------------------------------------------------------------
LABEL: SC_DISK_ERR2
IDENTIFIER: B6267342
Date/Time: Wed May 25 10:22:30 2016
Sequence Number: 80375
Machine Id: 00CE0C954C00
Node Id: ahyyhis
Class: H
Type: PERM
WPAR: Global
Resource Name: hdisk3
Resource Class:
Resource Type:
Location:
VPD:
Manufacturer................IBM
Machine Type and Model......1814 FAStT
ROS Level and ID............31303630
Serial Number...............
Device Specific.(Z0)........0000053245005032
Device Specific.(Z1)........
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
PATH ID
0
SENSE DATA
0600 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0012 0000 D980 0000 0000 0000 0000 0000 0000 0000 0093 0000
0000 003D 001A
---------------------------------------------------------------------------
LABEL: LVM_GS_RLEAVE
IDENTIFIER: AB59ABFF
Date/Time: Sat Apr 16 00:44:22 2016
Sequence Number: 80374
Machine Id: 00CE0C954C00
Node Id: ahyyhis
Class: U
Type: UNKN
WPAR: Global
Resource Name: LIBLVM
Resource Class: NONE
Resource Type: NONE
Location:
Description
Remote node Concurrent Volume Group failure detected
Probable Causes
Remote node Concurrent Volume Group forced offline
Failure Causes
Remote node left VGSA/VGDA groups due to failure
Recommended Actions
Examine error log on identified remote node
Detail Data
Remote Node Name
ahyyemr
Volume Group ID
00CE 0C95 0000 4C00 0000 0147 72B2 0EE6
MAJOR/MINOR DEVICE NUMBER
0034 0000
SENSE DATA
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
---------------------------------------------------------------------------
LABEL: LVM_GS_RLEAVE
IDENTIFIER: AB59ABFF
Date/Time: Sat Apr 16 00:44:11 2016
Sequence Number: 80373
Machine Id: 00CE0C954C00
Node Id: ahyyhis
Class: U
Type: UNKN
WPAR: Global
Resource Name: LIBLVM
Resource Class: NONE
Resource Type: NONE
Location:
Description
Remote node Concurrent Volume Group failure detected
Probable Causes
Remote node Concurrent Volume Group forced offline
Failure Causes
Remote node left VGSA/VGDA groups due to failure
Recommended Actions
Examine error log on identified remote node
Detail Data
Remote Node Name
ahyyemr
Volume Group ID
00CE 0C95 0000 4C00 0000 0147 72B2 0EE6
MAJOR/MINOR DEVICE NUMBER
0034 0000
SENSE DATA
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
---------------------------------------------------------------------------
LABEL: SC_DISK_ERR2
IDENTIFIER: B6267342
Date/Time: Thu Apr 7 11:03:37 2016
Sequence Number: 80372
Machine Id: 00CE0C954C00
Node Id: ahyyhis
Class: H
Type: PERM
WPAR: Global
Resource Name: hdisk5
Resource Class:
Resource Type:
Location:
VPD:
Manufacturer................IBM
Machine Type and Model......1814 FAStT
ROS Level and ID............31303630
Serial Number...............
Device Specific.(Z0)........0000053245005032
Device Specific.(Z1)........
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
PATH ID
0
SENSE DATA
0A00 2800 0000 0007 0000 0104 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0009 0002 6BC0 0000 0000 0000 0000 0000 0000 0000 0093 0000
0000 003D 0017
---------------------------------------------------------------------------
收起这个报错就是说有磁盘锁冲突,节点一在用,节点二有进程试图获取磁盘,因为锁在节点一上,所以也不会有什么问题,就是报错比较难看。
如果想解决,俩办法:
1。一般DS5000官方建议使用enhanced concurrent vg,这样没有磁盘锁,也不会有报错,一般这种操作都是一些扫盘或者读磁盘状态的进程,所以问题不大。
2。这个问题还是说一些版本低的系统里有一些bug,导致一些扫盘或者读取状态的进行需要改变锁状态,所以,升级到更高版本也可以解决相应问题。