Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: ASM and RAW Devices on RHEL 4
One thing to be aware of (I got caught with this one just yesterday!) is the 50-udev.permissions file seems to be read from the bottom up. Either that or wildcards take precedence. I left the line in there that says
raw/*:root:disk:0660
Having lines like this below that line seem to just be ignored:
raw/raw12:crsha:oinstall:0644 raw/raw22:crsha:oinstall:0644 raw/raw42:crsha:oinstall:0644 raw/raw11:root:oinstall:0660 raw/raw21:root:oinstall:0660
You need to comment out the wildcard line (i.e. #raw/*:root:disk:0660) for it to work.
Note I did absolutely minimal testing to prove this. A reboot without the wildcard line commented out didn't change the permissions correctly, a reboot with the wildcard did. Maybe someone with more RH4 knowledge than me can say why this happens, I was just in a hurry to MAKE it happen. :)
Pete
"Controlling developers is like herding cats." Kevin Loney, Oracle DBA Handbook
"Oh no, it's not. It's much harder than that!"
Bruce Pihlamae, long-term Oracle DBA
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of johan Eriksson
Sent: Wednesday, 8 March 2006 11:03 PM
To: Pete Sharman
Cc: bob_murching_at_budco.com; sanstorage_at_gmail.com; exriscer_at_gmail.com; Oracle-L Freelists
Subject: RE: ASM and RAW Devices on RHEL 4
On Wed, 2006-03-08 at 06:30 +1100, Pete Sharman wrote:
> Are they disappearing completely or is the protection mapping the
> issue? In RH4 raw devices are remapped on startup so you need to edit
> he /etc/udev/permissions.d/50-udev.permissions file so that the OCR
> devices are set up as root:oinstall:660 and the voting devices
> <crs_kernel_owner>:oinstall:644 (or something like that, check the
> install guide for correct protections).
>
>
or adding something like this to /etc/rc.local (raw1 OCR and raw2 is
voting), which I think is what the installation docs suggests.
chown root:oinstall /dev/raw/raw1
chmod 660 /dev/raw/raw1
chown oracle:oinstall /dev/raw/raw2
chmod 660 /dev/raw/raw2
chown oracle:oinstall /dev/sdb1
chown oracle:oinstall /dev/sdb2
chmod 660 /dev/sdb1
chmod 660 /dev/sdb2
But editing /etc/udev/permissions.d/50-udev.permissions is a more elegant solution I think (and new to me).
/johan
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Wed Mar 08 2006 - 09:21:36 CST
![]() |
![]() |