Installing RAC permissions bindings on CENTOS6

Your environment is as follows:

[[EMAIL PROTECTED] ~]# LL /DEV/MAPPER/*CRW-RW---- 1 root root 10,  58 Oct 24 07:59 /dev/mapper/controllrwxrwxrwx 1 root root       7 OCT 26 09:19 /DEV/MAPPER/DG ->&NBSP, .... /dm-0lrwxrwxrwx 1 root root      7 oct 26 09:19  /DEV/MAPPER/OCR ->&NBSP, .... /DM-1[[EMAIL PROTECTED] ~]# LL /DEV/DM-*BRW-RW---- 1 grid asmadmin 253 ,  0 OCT 26 09:43 /DEV/DM-0BRW-RW---- 1 grid asmadmin 253, 1  oct 26 09:43 /dev/dm-1[[email protected] ~]# more /etc/multipath.conf  defaults {user_friendly_names       yesmax_fds                    maxqueue_without_daemon      noflush_on_last_del          yes}multipaths  {                     multipath {                    wwid  14f504e46494c4552736437624e562d55494b362d5130656e                    alias ocr             }             multipath {                    wwid 14f504e46494c45525742544e57792d3349514d2d5472315a                    alias dg             }}[[email protected] ~]# more /etc/udev/rules.d/12-dm-permissions.rules       60-raw.rules                  90-alsa.rules                 98-kexec.rules                60-fprint-autosuspend.rules  70-persistent-cd.rules        90-hal.rules                  99-fuse.rules                 60-pcmcia.rules               70-persistent-net.rules      97-bluetooth-serial.rules    [[ email protected] ~]# more /etc/udev/rules.d/12-dm-permissions.rules env{dm_name}== "DG ",  owner:=" grid ",  group:=" Asmadmin ",  mode:=" 0660 ",  symlink+=" iscsi/oraasm-$env {DM_NAME} " env{dm_name}== "OCR",  owner:= "grid",  group:= "Asmadmin",  mode:= "0660",  symlink+= "iscsi/ oraasm-$env {Dm_name} "

Reprint a post: About RHEL6 Install RAC permissions binding issue

Red Hat Enterprise Linux 6.0 begins to discard the mode, UID, and GID parameters in the/etc/multipath.conf configuration file. The permissions of the Device-mapper device (including the multipath mapping) are set by Udev rules, and in the process of installing RAC, the granting of permissions is a troublesome problem, in general, Whether it is RHEL5 or RHEL6 we will use Udev to control the permissions to do a good job in RHEL6 under the two ways to control the disk permissions

Method One:

If you are using a multi-path software that comes with Linux, we can use the following:

/usr/share/doc/device-mapper-version has a template file named 12-dm-permissions.rules that we can use and put in the/ETC/UDEV/RULES.D directory for it to take effect

The main thing is to modify the following content, such as:

env{dm_name}== "Mpatha", owner:= "grid", group:= "Oinstall", mode:= "660"

If you specify an alias for a multipath device, such as the/etc/multipath.conf configuration is as follows

multipath {

Wwid 360050763008101d4e00000000000000a

Alias OCR

The 12-dm-permissions.rules need to replace the default mpath* with aliases such as:

env{dm_name}== "OCR", owner:= "grid", group:= "Oinstall", mode:= "660"

After the configuration is complete, execute udevadm trigge to make the configuration effective, and if not, use Start_udev

[Email protected] ~]# Udevadm trigger

Check that the DM device permissions are correct

[Email protected] rules.d]# ll/dev/dm*

Method Two:

If you are using a multi-path software that comes with storage, such as multi-path software for HDS storage:

is used in the/etc/udev/rules.d/99-oracle-asmdevices.rules

kernel== "sddlmac*", owner= "grid", group= "Oinstall", mode= "0660"

kernel== "sddlmaa*", owner= "grid", group= "Oinstall", mode= "0660"

kernel== "sddlmab*", owner= "grid", group= "Oinstall", mode= "0660"

If you are using a Linux-brought multipath software dm-multipath you need to first obtain the UUID number that is stored on the device:

For example, we created the following devices through Multipath:

OCRVOTE1P1 ocrvote2p1 ocrvote3p1 db1p1 db2p1 frap1 REDOP1

Get the UUID with the following command:

# for I in OCRVOTE1P1 ocrvote2p1 ocrvote3p1 db1p1 db2p1 frap1 redop1; Do

printf "%s%s\n" "$i" "$ (udevadm info--query=all--name=/dev/mapper/$i |

Grep-i dm_uuid) "; Done

The results are similar to the following:

OCRVOTE1P1 e:dm_uuid=part1-mpath-3600c0ff000dabfe596a0f65101000000

OCRVOTE2P1 e:dm_uuid=part1-mpath-3600c0ff000dabfe5a2a0f65101000000

OCRVOTE3P1 e:dm_uuid=part1-mpath-3600c0ff000dabfe5b4a0f65101000000

DB1P1 e:dm_uuid=part1-mpath-3600c0ff000d7e7a854a0f65101000000

DB2P1 e:dm_uuid=part1-mpath-3600c0ff000dabfe562a0f65101000000

Frap1 e:dm_uuid=part1-mpath-3600c0ff000d7e7a874a0f65101000000

REDOP1 e:dm_uuid=part1-mpath-3600c0ff000dabfe585a0f65101000000

So we'll do the following editing under/etc/udev/rules.d/99-oracle-asmdevices.rules:

kernel== "dm-*", env{dm_uuid}== "part1-mpath-3600c0ff000dabfe5f4d8515101000000", owner= "grid", GROUP= "Oinstall", Mode= "0660"

Add each piece of information above

In either of these ways, we can bind Multipath device permissions and ensure that they are not changed

It is recommended to use the multi-path software that comes with storage

This article is from the "just out of the shell of the Birds" blog, please be sure to keep this source http://qhd2004.blog.51cto.com/629417/1866011

Installing RAC permissions bindings on CENTOS6