Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Getting udev with multi-pathing to work on RHEL5 for ASM

Steve_WoodMar 25 2015 — edited Mar 25 2015

Hi All

I have real problems getting my udev rules to work with my multipath device paths for use with Oracle ASM. On RHEL6 it works just fine but on RHEL5 it just doesn't work. Does anyone have any working syntax examples on RHEL5 to share with me please? If anyone has these for EMC Powerpath I'd like those too although right now I'm on a server with native Linux multi-pathing.

I have tried all of the following in my /etc/udev/rules.d/96-oracleasm.rules file after which I run these commands "udevcontrol reload_rules" & "udevtrigger" but never see any new disk aliases appear. The multipath device I am trying to use is /dev/mapper/mpath8p1 it has the 'p1' on the end as I have created a single partition on it so that the sys admins don't confuse it with unused storage. These rules aren't in the file at the same time, I comment out the others when testing. If it's relevant I also have the oracleasm lib running that's providing the current device name persistence  for the other in-use disks but we want to move away from this as we often update our kernel version.

ACTION=="add|change", ENV{DM_UUID}=="part1-mpath-36006016072502a00f0d81cc9f8c4e111",SYMLINK+="oracleasm/disks/DSK0", GROUP="oinstall", OWNER="oracle", MODE="0660"

KERNEL=="sd*", PROGRAM=="scsi_id --page=0x83 --whitelisted --device=/dev/%k", RESULT=="36006016072502a00f0d81cc9f8c4e111", SYMLINK+="oracleasm/disks/DSK1", OWNER="oracle", GROUP="oinstall", MODE="0660"

KERNEL=="mapper/mpath8" SUBSYSTEM=="block", PROGRAM=="/sbin/scsi_id -g -u /dev/mapper/mpath8p1", RESULT=="36006016046502a002277a728e8c7e411", NAME="oracleasm/disks/DSK2", OWNER="oracle", GROUP="dba", MODE="0660"

SUBSYSTEM=="block", KERNEL=="mpath8p1", GROUP="oinstall", OWNER="oracle", MODE="0640", SYMLINK+="oracleasm/disks/DSK2"

ENV{DM_NAME}=="mpath8p1", ENV{ID_SERIAL}=="36006016072502a00f0d81cc9f8c4e111", NAME="oracleasm/disks/DSK3", OWNER="oracle", GROUP="oinstall", MODE="0660"

KERNEL=="dm-*", PROGRAM="scsi_id --page=0x83 --whitelisted --device=/dev/%k",RESULT=="36006016072502a00f0d81cc9f8c4e111", OWNER="oracle", GROUP="oinstall", MODE="0660", NAME="oracleasm/disks/DSK4"

Here is some output showing my the details and UUID of the disk

[root@some_srv ~]# multipath -ll | grep -A 5 mpath8

mpath8 (36006016072502a00f0d81cc9f8c4e111) dm-17 DGC,VRAID

[size=200G][features=0][hwhandler=1 alua][rw]

\_ round-robin 0 [prio=50][active]

\_ 2:0:1:8  sday       67:32  [active][ready]

\_ 1:0:0:8  sdi        8:128  [active][ready]

\_ round-robin 0 [prio=10][enabled]

[root@some_srv ~]#

[root@some_srv ~]# udevinfo -q all -p /sys/block/sday

P: /block/sday

N: sday

S: disk/by-id/scsi-36006016072502a00f0d81cc9f8c4e111

S: disk/by-path/pci-0000:06:00.1-fc-0x5006016746e0146d:0x0008000000000000

E: ID_VENDOR=DGC

E: ID_MODEL=VRAID

E: ID_REVISION=0430

E: ID_SERIAL=36006016072502a00f0d81cc9f8c4e111

E: ID_SERIAL_SHORT=6006016072502a00f0d81cc9f8c4e111

E: ID_TYPE=disk

E: ID_BUS=scsi

E: ID_PATH=pci-0000:06:00.1-fc-0x5006016746e0146d:0x0008000000000000

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 22 2015
Added on Mar 25 2015
3 comments
1,174 views