Udev vs. RHEL5 vs. 11gR2 vs. no ASM Lib

Question

Cross-posted by request from the Installation forums.
Hi, there,
I'm not a Linux guru, so you might have to bear with me on this one. Also, I don't want to use ASMLib due to previous bad experiences and a team policy to move away from it.
I've installed 11gR2 with Grid Infrastructure on a VMWare Virtual Machine running RHEL 5.6. I notice that upon restart, the raw devices that I use for my ASM disks have their ownership reset to root instead of oracle. This then stops the disk groups from mounting (obviously).
ls -lrt /dev/sd?1
brw-r----- 1 root disk 8, 81 Feb 8 17:04 /dev/sdf1
brw-r----- 1 root disk 8, 65 Feb 8 17:04 /dev/sde1
brw-r----- 1 root disk 8, 49 Feb 8 17:04 /dev/sdd1
brw-r----- 1 root disk 8, 33 Feb 8 17:04 /dev/sdc1
brw-r----- 1 root disk 8, 17 Feb 8 17:04 /dev/sdb1
From what I gather RHEL5 (we're running 5.6) helpfully automatically resets the ownership on /dev/ devices unless you tell it to set the permissions on startup through udev.
So I created a file in the correct directory
ls -lrt /etc/udev/rules.d
total 100
-rw-r--r-- 1 root root 1088 Jul 17 2006 60-pcmcia.rules
-rw-r--r-- 1 root root 2319 Jul 9 2008 bluetooth.rules
-rw-r--r-- 1 root root 114 Aug 28 2008 90-alsa.rules
-rw-r--r-- 1 root root 1823 Sep 18 2008 85-pcscd_ccid.rules
-rw-r--r-- 1 root root 316 Sep 22 07:27 60-raw.rules
-rw-r--r-- 1 root root 143 Oct 13 09:36 60-net.rules
-rw-r--r-- 1 root root 82 Nov 4 06:45 90-hal.rules
-rw-r--r-- 1 root root 9175 Nov 12 11:39 60-wacom.rules
-rw-r--r-- 1 root root 107 Nov 25 09:28 95-pam-console.rules
-rw-r--r-- 1 root root 61 Nov 25 09:28 90-dm.rules
-rw-r--r-- 1 root root 471 Nov 25 09:28 51-hotplug.rules
-rw-r--r-- 1 root root 16153 Nov 25 09:28 50-udev.rules
-rw-r--r-- 1 root root 515 Nov 25 09:28 05-udev-early.rules
-rw-r--r-- 1 root root 214 Nov 29 11:25 61-uinput-wacom.rules
-rw-r--r-- 1 root root 129 Nov 29 11:25 61-uinput-stddev.rules
-rw-r--r-- 1 root root 948 Dec 7 13:44 40-multipath.rules
-rw-r--r-- 1 root root 292 Jan 13 00:33 98-kexec.rules
-rw-r--r-- 1 root root 813 Jan 31 15:37 99-vmware-scsi-udev.rules
-rw-r--r-- 1 root root 128 Feb 8 10:18 55-usm.rules
-rw-r--r-- 1 root root 305 Feb 8 16:42 97-oracle.rules
My 97-oracle.rules seems to be ignored. It comprises of the following:
more 97-oracle.rules
KERNEL=="/dev/sdf1", OWNER="oracle", GROUP="dba", MODE="660"
KERNEL=="/dev/sde1", OWNER="oracle", GROUP="dba", MODE="660"
KERNEL=="/dev/sdd1", OWNER="oracle", GROUP="dba", MODE="660"
KERNEL=="/dev/sdc1", OWNER="oracle", GROUP="dba", MODE="660"
KERNEL=="/dev/sdb1", OWNER="oracle", GROUP="dba", MODE="660"
These are ASM disks, so I set the mode to 660 as per the documentation.
I know I can fix this the cheap way by calling a script from rc.d which will chown the devices before my Oracle processes start. But is there a more fulfilling and satisfying way of doing this (again, avoiding ASMLib).
Mark

Answer 1

>
more 97-oracle.rules
KERNEL=="/dev/sdf1", OWNER="oracle", GROUP="dba", MODE="660"
KERNEL=="/dev/sde1", OWNER="oracle", GROUP="dba", MODE="660"
KERNEL=="/dev/sdd1", OWNER="oracle", GROUP="dba", MODE="660"
KERNEL=="/dev/sdc1", OWNER="oracle", GROUP="dba", MODE="660"
KERNEL=="/dev/sdb1", OWNER="oracle", GROUP="dba", MODE="660"
MarkHi Mark,
Try this one
KERNEL=="sdf1", BUS=="scsi", NAME="asmdisk1", ACTION=="add|change", OWNER="oracle", GROUP="dba", MODE="0660"Cheers